Recover from closed sink/closed connection #174
Merged
+106
−20
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.
I'm not 100% convinced that silently restoring the sink + connection is the correct approach, but it doesn't happen very often and we aren't going to lose much output if we immediately re-open the sink + connection.
Fixes #104 (at least as much as it can be fixed)
It's also worth noting that we're already in a much better place than the released version because we're opening and closing the sink once per chunk, rather than once per top-level expression. That means that you can now use
sink()
within a chunk, which I've added a test for. This PR only affects the behaviour of unbalanced sinks, either closing a sink you didn't open, or opening a sink that you don't close.