Issue calling Child.output() on ubuntu-latest with v1.8.0
#55
Comments
This was referenced Sep 30, 2023
|
Thanks for the report, and sorry for the breakage! I've yanked 1.8.0. cc @notgull |
|
This might be the same issue as I've encountered in #54. It looks like it's missing the |
notgull
added a commit
to smol-rs/async-signal
that referenced
this issue
Sep 30, 2023
This backend appears to miss some signals that are raised on other threads. This might be the cause of smol-rs/async-process#55. I don't feel like kneading signalfd into a better shape, and it probably isn't much of an improvement over the pipe strategy anyways. So I've just removed it. Signed-off-by: John Nunley <dev@notgull.net>
notgull
added a commit
to smol-rs/async-signal
that referenced
this issue
Oct 2, 2023
This backend appears to miss some signals that are raised on other threads. This might be the cause of smol-rs/async-process#55. I don't feel like kneading signalfd into a better shape, and it probably isn't much of an improvement over the pipe strategy anyways. So I've just removed it. Signed-off-by: John Nunley <dev@notgull.net>
|
@shariffdev Can you re-run the tests with the latest master? I believe that smol-rs/async-signal#20 fixed this issue. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We encountered an unexpected problem when using
async-processon theubuntu-latestenvironment in our CI workflow after it was updated to versionv1.8.0on September 25th.The issue manifests as erratic behaviour in our code, primarily blocking, when we make calls to
Child.output(). We would appreciate any assistance in troubleshooting and resolving it. If you need any further information or logs, please let us know.Associated Issue: near/near-workspaces-rs#312
The text was updated successfully, but these errors were encountered: