refactor torProvider: merge networkStatus and BootstrapStatus, simplify monitorRestart logic. Catch case due to magic numbers where it was not restarting tor when tor was killed #3

dan · 2020-05-12T21:37:17Z

dan commented

2020-05-12 21:37:17 +00:00

I'm a derp. using magic numbers missed a -1 to -2 so torProvider wasn't restarting tor when it was dead. Fixed that and refactored a bit more:

tested again with cwtch ui

doesn't cycle tor when network-liveness reports down. does cycle tor when tor is killed

manages restarts in both cases, either redetecting network up and resuming at 100 progress or restarting tor fully

I'm a derp. using magic numbers missed a -1 to -2 so torProvider wasn't restarting tor when it was dead. Fixed that and refactored a bit more: tested again with cwtch ui doesn't cycle tor when network-liveness reports down. does cycle tor when tor is `kill`ed manages restarts in both cases, either redetecting network up and resuming at 100 progress or restarting tor fully

sarah was assigned by dan

2020-05-12 21:37:17 +00:00

sarah referenced this issue from a commit

2020-05-12 21:50:58 +00:00

Merge pull request 'refactor torProvider: merge networkStatus and BootstrapStatus, simplify monitorRestart logic. Catch case due to magic numbers where it was not restarting tor when tor was killed' (#3) from restart into master

sarah closed this pull request

2020-05-12 21:50:58 +00:00

Sign in to join this conversation.

No reviewers