ad2fb4b297
In order to minimize this change while keeping a simple version of the behavior, we set `lastOk` to the current time less the intial server connection timeout. If the client starts and never contacts the server, it will stop all configured tasks after the initial server connection grace period, on the assumption that we've been out of touch longer than any configured `stop_after_client_disconnect`. The more complex state behavior might be justified later, but we should learn about failure modes first. |
||
|---|---|---|
| .. | ||
| testdata | ||
| 08types.go | ||
| db_test.go | ||
| errdb.go | ||
| interface.go | ||
| memdb.go | ||
| noopdb.go | ||
| state_database.go | ||
| upgrade.go | ||
| upgrade_int_test.go | ||
| upgrade_test.go | ||