-
Notifications
You must be signed in to change notification settings - Fork 204
New timeout config options [ADR 006] #745
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
New timeout config options [ADR 006] #745
Conversation
It should retry finding an idle connection after being woken up
a805f38 to
07f8bb2
Compare
07f8bb2 to
43ddb35
Compare
32d6de1 to
56b7b53
Compare
|
Stub tests are expected to fail because of the UTC fix not being implemented in the Driver yet. |
| acquire_kwargs_ = { | ||
| "access_mode": access_mode, | ||
| "timeout": self._config.connection_acquisition_timeout, | ||
| "timeout": timeout, |
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.
It feels a bit strange to figure out what is happen here, because of the timeout field being filled with a Deadline. It's not a major issue, since the code knows how to handle it.
bigmontz
left a comment
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.
⏲️ 💥
ac6ded7 to
4f8190d
Compare
4f8190d to
74b06ee
Compare
|
multi-db Integration tests with 5.0 are failing because the async nature of db management procedure changed (neo4j-drivers/testkit#484) -> unrelated to this change. |
* Backport new connection timeout config options Backport of #745
Amends #675
Implements ADR 006 (internal reference)