Skip to content

Conversation

robsdedude
Copy link
Member

  • ValueError on invalid values (instead of ClientError)
  • Consistently restrict the value to be strictly positive

 - `ValueError` on invalid values (instead of `ClientError`)
 - Consistently restrict the value to be strictly positive
@robsdedude robsdedude force-pushed the errors/value-error-on-invalid-acquisition-timeout branch from a3cbd46 to 5783295 Compare April 29, 2025 08:49
Signed-off-by: Rouven Bauer <[email protected]>
@robsdedude robsdedude force-pushed the errors/value-error-on-invalid-acquisition-timeout branch from 595d626 to 02f55ae Compare May 13, 2025 07:39
Copy link
Contributor

@AndyHeap-NeoTech AndyHeap-NeoTech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good.

@robsdedude robsdedude enabled auto-merge (squash) May 13, 2025 08:37
@robsdedude robsdedude disabled auto-merge May 13, 2025 08:37
@robsdedude robsdedude merged commit 7b07121 into neo4j:6.x May 13, 2025
20 checks passed
@robsdedude robsdedude deleted the errors/value-error-on-invalid-acquisition-timeout branch May 13, 2025 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants