Async scheduler / execution expired #443
Replies: 2 comments
-
|
Yes, that looks correct. The timeout fires while the client is waiting for the response: are the two key lines. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok, great. Thanks for the sanity check! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey @ioquatix,
I'm kind of just looking for some validation for a timeout error I am seeing:
I am trying to figure out what's really happening here... so there's a timeout value that is set as part of the Faraday adapter that is ultimately being used as the total time this request takes to return? What confuses me is that this ultimately times out with
IO::Event::Selector::URing#transfer? Is that expected?Beta Was this translation helpful? Give feedback.
All reactions