rust/library/std/src/sys/solid, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2024-01-11T19:10:25+00:00std: begin moving platform support modules into `pal`2024-01-11T19:10:25+00:00joboetjonasboettiger@icloud.com2024-01-11T19:10:25+00:00urn:sha1:99128b7e45f8b95d962da2e6ea584767f0c85455kmc-solid: Implement `{From,Into}Inner<OwnedFd>` for `Socket`2023-11-08T01:51:59+00:00Tomoaki Kawadakawada@kmckk.co.jp2023-08-23T10:06:43+00:00urn:sha1:46bc247bd145f3357acb07b7f146ec9514e0a193kmc-solid: Remove `FileDesc`2023-11-08T01:51:57+00:00Tomoaki Kawadakawada@kmckk.co.jp2023-11-08T01:51:57+00:00urn:sha1:6d1e4ddf0354e51e3520abfbd32a394f497d3f3b
Removes the private type `std::sys::solid::net::FileDesc`, replacing its
only usage in `std::sys::solid::net::Socket` with `std::os::solid::io::
OwnedFd`.
kmc-solid: Replace `{From,Into}Inner<c_int>` impls with `*RawFd` for `Socket`2023-11-08T01:48:49+00:00Tomoaki Kawadakawada@kmckk.co.jp2023-08-23T10:07:18+00:00urn:sha1:cbfab81f3d3fe678c20ed8861fcddda98198db68
Follows how other targets are implemented.
Auto merge of #116132 - darthunix:connect_poll, r=cuviper2023-10-19T11:22:28+00:00borsbors@rust-lang.org2023-10-19T11:22:28+00:00urn:sha1:3fbcfd2b6f7030cb70328aa759107efc1516912c
Make TCP connect handle EINTR correctly
According to the [POSIX](https://pubs.opengroup.org/onlinepubs/009695399/functions/connect.html) standard, if connect() is interrupted by a signal that is caught while blocked waiting to establish a connection, connect() shall fail and set errno to EINTR, but the connection request shall not be aborted, and the connection shall be established asynchronously. When the connection has been established asynchronously, select() and poll() shall indicate that the file descriptor for the socket is ready for writing.
The previous implementation differs from the recomendation: in a case of the EINTR we tried to reconnect in a loop and sometimes get EISCONN error (this problem was originally detected on MacOS).
1. More details about the problem in an [article](http://www.madore.org/~david/computers/connect-intr.html).
2. The original [issue](https://git.picodata.io/picodata/picodata/tarantool-module/-/issues/157).
Make TCP connect() handle EINTR correctly2023-10-13T11:12:56+00:00Denis Smirnovsd@picodata.io2023-10-05T09:04:28+00:00urn:sha1:dfadd177a9738de289a3a6d4b39c08d94f384c1a
According to the POSIX standard, if connect() is interrupted by a
signal that is caught while blocked waiting to establish a connection,
connect() shall fail and set errno to EINTR, but the connection
request shall not be aborted, and the connection shall be established
asynchronously.
If asynchronous connection was successfully established after EINTR
and before the next connection attempt, OS returns EISCONN that was
handled as an error before. This behavior is fixed now and we handle
it as success.
The problem affects MacOS users: Linux doesn't return EISCONN in this
case, Windows connect() can not be interrupted without an old-fashoin
WSACancelBlockingCall function that is not used in the library.
So current solution gives connect() as OS specific implementation.
std: abort instead of panicking if the global allocator uses TLS2023-10-04T09:49:48+00:00joboetjonasboettiger@icloud.com2023-10-04T09:49:48+00:00urn:sha1:b18990b1e973a1fd0a0318a88655dc1907509b17std: panic when the global allocator tries to register a TLS destructor2023-10-03T21:57:37+00:00joboetjonasboettiger@icloud.com2023-10-03T21:13:55+00:00urn:sha1:fd23276ca87b4b56918e4a87737859cfd77d657ckmc-solid: Refactor `is_interrupted` to avoid integer overflow2023-09-01T02:55:48+00:00Tomoaki Kawadakawada@kmckk.co.jp2023-09-01T02:55:48+00:00urn:sha1:eb627ea3392c37cd94e7696dca683ef596c8b66ckmc-solid: Directly delegate to `net::is_interrupted` in `std::sys::solid::is_interrupted`2023-09-01T02:53:15+00:00Tomoaki Kawadakawada@kmckk.co.jp2023-09-01T02:43:48+00:00urn:sha1:dc37959ce858e1c3a872449cf289c9d9fa2efd2e