-
Notifications
You must be signed in to change notification settings - Fork 197
getsockname fails: 'NoneType' object is not subscriptable #1057
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
Hi @ccloes and thanks for sharing the stack trace. This is a very unexpected code-path, I must admit. Right after the async socket has been opened, I was not able to reproduce this condition locally, so can you please provide me with additional information that should help me pin-point how this came to be:
|
One last attempt as I'd really like to dig into this issue but can't reproduce it on my own. @ccloes please help me (see comment above). |
@MarkPAndrews can you help us get this reviewed? |
@robsdedude sorry for the delay... we are asking for Mark with Neo4j to help get this worked. |
We discussed with this the Neo4j team, and we are going to try and push this to later when we revisit hardening the connector code in Nodestream and doing some of the performance testing work that is planned. The issue manifested itself under high load, and when leader elections were happening on the database side. We can close this ticket for now until we are better able to reproduce the issue. |
Thank you for coming back on this. As you suggested, I'll close this issue for now. For future you or anyone else coming across this issue: feel free to reopen this issue while providing the additional information requested in my earlier comment. The linked custom driver version might not exist anymore though. |
Originally posted by @ccloes in #730 (comment)
The text was updated successfully, but these errors were encountered: