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
It turns out that libuv processes register SIGCHLD handlers, but these handlers aren't registered with SA_RESTART, so when we receive a SIGCHLD syscalls are interrupted and std::io doesn't handle the EINTR return value. Currently the tests which exercise libuv process bindings are ignored, and they currently aren't used anywhere else in the code.
We have two options to un-ignore these tests
Teach all of std::io and various libc bindings to handle EINTR
Wait for std::io to be removed.
I'm in favor of option 2, but mainly just because it means that it's less effort :)
The text was updated successfully, but these errors were encountered:
…rap_or, r=giraffate
suggest map_or in case_sensitive_file_extension_comparisons
changelog: [`case_sensitive_file_extension_comparisons `]: updated suggestion in the example to use `map_or`
Currently, case_sensitive_file_extension_comparisons suggests using `map(..).unwrap_or(..)` which trips up the `map_unwrap_or` lint. This updates the suggestion to use `map_or`.
It turns out that libuv processes register SIGCHLD handlers, but these handlers aren't registered with SA_RESTART, so when we receive a SIGCHLD syscalls are interrupted and
std::io
doesn't handle theEINTR
return value. Currently the tests which exercise libuv process bindings are ignored, and they currently aren't used anywhere else in the code.We have two options to un-ignore these tests
std::io
and variouslibc
bindings to handleEINTR
std::io
to be removed.I'm in favor of option 2, but mainly just because it means that it's less effort :)
The text was updated successfully, but these errors were encountered: