-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Reasonable Default for MaximumExecutionTimeInMs #487
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
Comments
+1 |
@skearns64 Thank you for the report. Assigning appropriately for resolution. |
@markcowl Can you provide an update on this? :) |
We are rewriting the core of the java sdk and should have a much better solution to this in the next major release. |
Thanks for the update, looking forward to the new version! |
Closing as resolved. JFYI, the development work of new SDK generation tool can be tracked in https://github.com/azure/autorest/tree/dev |
By default, it appears that there is no default set for MaximumExecutionTimeInMs.
In practice, some calls appear to never get a response from Azure, which results in the client hanging forever with default settings.
A default setting here, even if it were rather high, would make this library safer for clients to use. Most users won't know it isn't safe to use the library without setting this value, because you only see it as an issue when Azure drops a request, which doesn't appear to be often, but does happen.
The text was updated successfully, but these errors were encountered: