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
--- cinnabarclone.t
+++ cinnabarclone.t.err
@@ -110,7 +110,7 @@
Cloning into 'repo-git'...
Fetching cinnabar metadata from http://localhost:8080/
\r (no-eol) (esc)
- ERROR unable to access 'http://localhost:8080/': Failed to connect to localhost port 8080.* (re)
+ ERROR unable to access 'http://localhost:8080/': getsockname() failed with errno 22: Invalid argument
\r (no-eol) (esc)
WARNING Falling back to normal clone.
It looks like the string Failed to connect might come from here:
It seems that if connect() on a non-blocking socket is refused, connect() fails with EINPROGRESS everywhere whereas subsequent getsockname() succeeds with an all-zero sockaddr on Linux but fails with EINVAL on NetBSD.
(I have not yet determined whether this is a bug in the test, a bug in curl, or a bug in NetBSD/Linux; I'm just writing this down to create an initial record that can be searched and referenced.)
The text was updated successfully, but these errors were encountered:
0.7.0beta2 with curl-8.11.0 on NetBSD 9
It looks like the string
Failed to connect
might come from here:git-cinnabar/src/main.rs
Lines 856 to 857 in 4028262
Plausible source of the getsockname error is from curl in this logic:
https://github.com/curl/curl/blob/b1ef0e1a01c0bb6ee5367bd9c186a603bde3615a/lib/cf-socket.c#L1064-L1069
It seems that if connect() on a non-blocking socket is refused, connect() fails with EINPROGRESS everywhere whereas subsequent getsockname() succeeds with an all-zero sockaddr on Linux but fails with EINVAL on NetBSD.
(I have not yet determined whether this is a bug in the test, a bug in curl, or a bug in NetBSD/Linux; I'm just writing this down to create an initial record that can be searched and referenced.)
The text was updated successfully, but these errors were encountered: