Skip to content

Conversation

@RichardIrons-neo4j
Copy link
Contributor

@RichardIrons-neo4j RichardIrons-neo4j commented Oct 23, 2025

Also includes the removal of deprecated severity property.

Bookmarks bookmarks,
bool forceAuth)
{
return await AcquireConnectionInternalAsync(mode, database, sessionConfig, bookmarks, forceAuth)
Copy link
Contributor

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.

@RichardIrons-neo4j RichardIrons-neo4j merged commit 913a7c3 into neo4j:6.x Oct 24, 2025
5 of 7 checks passed
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