Skip to content

"WARNING: no socket in pollset, transfer may stall" for plain HTTP/3 #14047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bagder opened this issue Jun 28, 2024 · 1 comment
Closed

"WARNING: no socket in pollset, transfer may stall" for plain HTTP/3 #14047

bagder opened this issue Jun 28, 2024 · 1 comment
Assignees
@icing
Labels
HTTP/3 h3 or quic related

Comments

@bagder
Copy link
Member

bagder commented Jun 28, 2024

I did this

With an ngtcp2-enabled build:

curl -v --http3 https://graph.oculus.com -o /dev/null

...
* IPv6: 2a03:2880:f20a:c1:face:b00c:0:32c2
* IPv4: 31.13.72.51
* WARNING: no socket in pollset, transfer may stall!
* STATE: RESOLVING => CONNECTING handle 0x55a4f0b39cd8; line 2047

I expected the following

The warning is not expected to show!

curl/libcurl version

git master (curl-8_8_0-259-g9acf759455)

operating system

Debian Linux
@bagder bagder added the HTTP/3 h3 or quic related label Jun 28, 2024
@icing icing mentioned this issue Jul 1, 2024
Closed
@icing
Copy link
Contributor

icing commented Jul 1, 2024

See #14074 for the fix. This happened when the RESOLVING phase did not wait for any sockets and was not HTTP/3 specific.

@bagder bagder closed this as completed in 480883c Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@icing icing

Labels
HTTP/3 h3 or quic related
Milestone
No milestone
Development

No branches or pull requests
2 participants
@icing @bagder