Allow farmer to start quickly in dev environment and shut down quickly once node RPC disconnects #2535
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setting sync to paused unconditionally may result in node being stuck waiting until DSN sync notifications before identifying it is actually synced (this happens after some relatively recent changes where
sync_paused
is taken into consideration during major sync check).On farmer side when slot notification subscription ended, but no other RPC errors, farmer was just hanging until something else calls RPC and triggers exit this way, simply returning error at the end of the subscription stream fixes this.
Code contributor checklist: