-
Notifications
You must be signed in to change notification settings - Fork 3
api: TRANSFER_IN_PROGRESS error shoud be retryable #77
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
api: TRANSFER_IN_PROGRESS error shoud be retryable #77
Conversation
42c9235
to
461aaec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test for this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the library has moved to another team, the rules for formatting commits and changelog have changed a bit. Please update the commit message to something like this.
api: TRANSFER_IN_PROGRESS error shoud be retryable
Lua vshard router changed its behavior [1], we should conform.
1. https://github.com/tarantool/vshard/issues/548
Closes #75
and update the changelog entry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but would also like to see some tests. Thanks!
Lua vshard router changed its behavior [1], we should conform. 1. tarantool/vshard#548 Closes tarantool#75
96b87fe
to
7811eed
Compare
@oleg-jukovec I have updated the commit message and applied your suggestion about changelog entry. @RunsFor Unfortunately, the current testing framework doesn't allow to write tests for such complex scenario 😞 I have updated the PR description above and added this information. |
Lua vshard router changed its behavior [1], we should conform.
TRANSFER_IN_PROGRESS
error shoud be retryable vshard#548Closes #75
Unfortunately, no new tests are provided due to limitations of the current testing module. To provide tests for such complex cases, the current testing framework should be extended significantly.
I didn't forget about (remove if it is not applicable):
Related issues:
Resolve #75