You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks a lot for the great library!
I'm trying to migrate from my own half-baked implementation to your library and it feels much much better than anything I could've implemented myself!
There is one thing I cannot figure out yet. Is there an API to determine whether a child process signaled or not?
Currently, I can only see the exit status, but it is not very helpful since value 134 could mean either exit(134) or abort().
I would appreciate any hints on the subject.
Cheers,
Alex.
The text was updated successfully, but these errors were encountered:
reproc follows bash here so unfortunately, there isn't yet a way to determine whether a process exited because of a signal or normally.
It shouldn't be too hard to add though. We can store an extra property telling whether the process exited with a signal or not and expose it via a new function reproc_signalled(). I'd happily review a PR for that.
Hi @DaanDeMeyer,
First of all, thanks a lot for the great library!
I'm trying to migrate from my own half-baked implementation to your library and it feels much much better than anything I could've implemented myself!
There is one thing I cannot figure out yet. Is there an API to determine whether a child process signaled or not?
Currently, I can only see the exit status, but it is not very helpful since value 134 could mean either
exit(134)
orabort()
.I would appreciate any hints on the subject.
Cheers,
Alex.
The text was updated successfully, but these errors were encountered: