-
Notifications
You must be signed in to change notification settings - Fork 78
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
renew Session for session expired & reconnect connection of session for IOError #276
Labels
Comments
Sure, I can do this :) @Nicole00 |
like implementations from, with (exponential)backoff-wise retry based on different exceptions. |
wey-gu
added a commit
to wey-gu/nebula-python
that referenced
this issue
Jan 8, 2024
3 tasks
wey-gu
added a commit
that referenced
this issue
Jan 10, 2024
wey-gu
added a commit
to wey-gu/nebula-python
that referenced
this issue
Mar 4, 2024
Nicole00
pushed a commit
that referenced
this issue
Mar 4, 2024
* feat: renew session for expiration, re-execute when error close: #276 * ci: pdm fmt make black happy * fix: test cases failure * fix ssl cases * feat: add retry interval in seconds for seesion retry * chore: comments for py3.6 build from source ci * fix: missing sleep for json execution addressing review comments by @Nicole00 * fix: ci in py3.12 due to https://peps.python.org/pep-0632/ * call py3.12 examples without pdm * fix: remove pdm in example run due to 3.12 setuptools cannot fit >=py3.6.2 * use pip to build from source * fix: add dev and test group pdm installation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
add re-execute operation, before re-execute, we should renew the session if the failure is E_SESSION_INVALID or E_SESSION_TIMEOUT, and we should reconnect the session's connection for IO Error, and just re-execute for E_EXECUTION_ERROR.
Don't retry for E_STATEMENT_EMPTY and E_SYNTAX_ERROR.
The text was updated successfully, but these errors were encountered: