Don't call rx.next after receiving None, fixes #27 #28
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.
In case the channel is dropped, rx.next will return None once.
After that we must not call rx.next or else it will remind us
by panicking. Instead we leave now the restart loop, since
the channel is broken and restarting the actor won't help it.
The supervisor calls a last time .stopped on the actor and
supervising ends.
Unfortunately the doc test does not catch this errornous behaviour
since the panic happens in another thread. The main process still
exits with code 0. We only see the panic through lines on the
terminal.
fixes #27