Ipc failure while streaming #346
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
goodboy
force-pushed
the
ipc_failure_while_streaming
branch
from
c9f2d96 to
2aed7dd
Compare
Owner
Author
|
Lol.. ok so its 5dc07f0.. No idea why yet, but dropping that commit for this history and gonna rebase all dependents. |
goodboy
force-pushed
the
ipc_failure_while_streaming
branch
from
2aed7dd to
f7cc993
Compare
2 tasks
Owner
Author
|
Lul, and turns out ba6a2b1 causes the So gonna drop that one for now as well.. |
goodboy
force-pushed
the
ipc_failure_while_streaming
branch
from
f7cc993 to
6d34893
Compare
goodboy
force-pushed
the
ipc_failure_while_streaming
branch
from
6895172 to
b722238
Compare
goodboy
commented
Jan 27, 2023
| ): | ||
| # if we can't propagate the error that's a big boo boo | ||
| log.error( | ||
| log.exception( |
Owner
Author
There was a problem hiding this comment.
This is important to show what traceback wasn't able to be propagated to the far end actor's caller task.
goodboy
commented
Jan 27, 2023
| log.warning(text) | ||
| await send_chan.send(msg) | ||
| try: | ||
| await send_chan.send(msg) |
Owner
Author
There was a problem hiding this comment.
If using backpressure on a stream we need to be sure we don't crash when the local feed memchan has been broken.
Need a test for this, though I can't remember if this was the original issue that caused the ipc_failure_during_stream.py example to inf hang before?
goodboy
commented
Jan 27, 2023
tractor/_streaming.py
Outdated
| # far end. | ||
| await self.send_stop() | ||
| try: | ||
| await self.send_stop() |
Owner
Author
There was a problem hiding this comment.
Also need a test for this:
- one end of a stream is closed
- the other end trying to close before any other stream methods
.receive()/.send()are called (thus detecting the closure before trying to send a stop msg)
goodboy
commented
Jan 27, 2023
| finally: | ||
| # NOTE: this is ABSOLUTELY REQUIRED to avoid | ||
| # the following wacky bug: | ||
| # <tractorbugurlhere> |
Owner
Author
There was a problem hiding this comment.
I don't think I can remember the case that caused this unfortunately 😂 though pretty sure it was in piker.
Unfortunately this may just go in without a false positive case ..
Closed
goodboy
added
bug
When backpressure is used and a feeder mem chan breaks during msg delivery (usually because the IPC allocating task already terminated) instead of raising we simply warn as we do for the non-backpressure case. Also, add a proper `Actor.is_arbiter` test inside `._invoke()` to avoid doing an arbiter-registry lookup if the current actor **is** the registrar.
Use a task nursery in the subactor to spawn tasks which cancel the IPC channel mid stream to simulate the most concurrent case we're likely to see. Make `main()` accept a `debug_mode: bool` for parametrization. Fill out detailed comments/docs on this example.
With the new fancy `_pytest.pathlib.import_path()` we can do real parametrization of the example-script-module code and thus configure whether the child, parent, or both silently break the IPC connection. Parametrize the test for all the above mentioned cases as well as the case where the IPC never breaks but we still simulate the user hammering ctl-c / SIGINT to terminate the actor tree. Adjust expected errors based on each case and heavily document each of these.
We weren't doing this originally I *think* just because of the path dependent nature of the way the code was developed (originally being mega pedantic about one-way vs. bidirectional streams) but, it doesn't seem like there's any issue just calling the stream's `.aclose()`; also have the benefit of just being less code and logic checks B)
goodboy
force-pushed
the
ipc_failure_while_streaming
branch
from
710dee0 to
13c9ead
Compare
guilledk
approved these changes
Jan 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Variety of streaming related teardown fixes for when IPC goes down before streams are terminated gracefully. Mostly discovered during dev of initial draft of pikers/piker#420.
TODO:
OSError: [Errno 9] Bad file descriptorin cluster test #345 => dropping 5dc07f0 did it