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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
Just testing with the included CalcNative example.
Running it normally works but trying to simulate a request that would take longer to process on the server side (In this case adding a sleep of 10 seconds) causes the client to fail with "Failed to send request: broken promise".
Is there some sort of timeout setting or is this an issue?
The text was updated successfully, but these errors were encountered:
I figured out that you can increase the timeout like this: response = (*client)(std::move(request), std::chrono::milliseconds(30000)).get();
I feel like this needs to be documented.
Is there a reason for the variadic template transactionArgs? It only seems to be forwarded to BeginTransaction which only has an optional std::chrono::milliseconds argument. So transactionArgs can only really be a std::chrono::milliseconds object right now. Is it for future-proofing?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just testing with the included CalcNative example.
Running it normally works but trying to simulate a request that would take longer to process on the server side (In this case adding a sleep of 10 seconds) causes the client to fail with "Failed to send request: broken promise".
Is there some sort of timeout setting or is this an issue?
The text was updated successfully, but these errors were encountered: