-
Notifications
You must be signed in to change notification settings - Fork 197
Have a way to retrieve the original error on defunct connection ? #463
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
@prevostc Thanks for the suggestion, I will have a look at this, to improve error propagation for this case. |
@prevostc does the PR solve your issue with the error propagation info? I will do a patch release on Thursday where this is included. |
@martin-neotech thank you for your quick work and great communication. I'll try the branch with the fix and will let you know today. |
Sorry for the delay, I can confirm this fix for my particular issue |
great news, thanks for the feedback. Cheers, Martin |
Suggestion
I noticed the _set_defunct method of the bolt protocol files completely hides the underlying error message:
neo4j-python-driver/neo4j/io/_bolt4x0.py
Line 367 in 2d55eae
In my case I get a OSError from IncomingMessage:
neo4j-python-driver/neo4j/io/_bolt4x0.py
Line 85 in 2d55eae
neo4j-python-driver/neo4j/io/_courier.py
Line 63 in 2d55eae
When I get this "Failed to read from defunct connection" error, I don't really know what to do and have absolutely no way to retrieve the original error for hints.
The text was updated successfully, but these errors were encountered: