-
Couldn't load subscription status.
- Fork 69
Fix connection acquisition timeout #874
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
Conversation
Co-authored-by: Copilot <[email protected]>
… version settings, and modify Dockerfile for .NET SDK 9.0
…xceptionManager; update LoadBalancer to include driver context in connection acquisition.
| Bookmarks bookmarks, | ||
| bool forceAuth) | ||
| { | ||
| return await AcquireConnectionInternalAsync(mode, database, sessionConfig, bookmarks, forceAuth) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it the case that because AcquireConnectionInternalAsync does not observe a cancellationToken that the underlying operations might continue running after the await timesout? The timeout is effectively only impacting the awaiting task? The ConnectionAcquisition timeout is still being used on several steps lower down the stack (), so I'm wondering if the CancelationToken should be passed down the layers that way enforcing the timeout across all operations.
Also includes the removal of deprecated severity property.