-
Notifications
You must be signed in to change notification settings - Fork 174
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.
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
Cohttp-eio: response body not flushed? #1004
Comments
Ok the "bug" was on my side. For the historians: I had something that worked with 6.0.0~alpha1 and an earlier Eio that included being able to log the body of the response before sending it; with @talex5 should |
That's an interesting point about the name. However, it's not always a more (e.g. if the source is a file then the file data isn't deleted). |
Using the current
master
branch.I have server code that hangs with:
"hangs" =
curl
client hangs, the~stop
argument of the server (the_ Promise.t
) does not stop the server but the server logs show that it can handle more than one request.It seems better with:
"better = at least the client is "unlocked" and the
~stop
argument (the_ Promise.t
) does it's job. But the body is not actually transmitted.It seems that this loop in
cohttp-eio/src/utils.ml
exits before sending any bytes:This is the debug output (in both cases of
~body:
argument):Any ideas?
(Eio 0.13, OCaml 5.1)
The text was updated successfully, but these errors were encountered: