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
Are you ok with non-simultaneous reading and writing of the request
and response? In practice this means a server that sends an error
response and then hangs up before reading the full request would cause
your client to only receive the write error, and not the actual
response.
That sounds like an appropriate tradeoff. That's obviously lighter weight than doing something like spinning up a throwaway thread for doing them synchronously and covers almost all of the use cases. If you want something else set up a scheduler.
hmm, how hard would it be to get the network/http library tests running both with a scheduler and with no scheduler? i fixed this issue only to find a few more places where an iomanager is assumed (Socket::cancelIo for example)
request() assumes it is being called from a fiber, which is not necessarily the case.
the last line segfaults, since getThis() returns NULL
The text was updated successfully, but these errors were encountered: