Skip to content
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

fix: overload dump_write_request shouldn't auto-reply to client #718

Merged
merged 5 commits into from
Apr 13, 2021

Conversation

foreverneverer
Copy link
Contributor

@foreverneverer foreverneverer commented Apr 9, 2021

What problem does this PR solve?

#533 overload dump_write_request for XiaoMi/rdsn#414 and cause the problem that the server will auto-reply to client with ERR_OK, so all the response_client_write after dump_write_request will be ignored for client, it also mean client will always receive ERR_OK, though pass ERR_INVALID_DATA in XiaoMi/rdsn#414.

What is changed and how does it work?

This PR use rpc_holder constructor replace rpc::auto_replayto dump request

Checklist

  • Manual test (add detailed scripts or steps below)
Side effects
  • large write request will be responsed with ERR_INVALID_DATA and throw exception at client side
Related changes
  • Need to cherry-pick to the release branch
  • Need to update the documentation
  • Need to be included in the release note

levy5307
levy5307 previously approved these changes Apr 9, 2021
@neverchanje
Copy link
Contributor

Good job. Is there any case of bug caused by this problem?

@foreverneverer
Copy link
Contributor Author

foreverneverer commented Apr 13, 2021

Good job. Is there any case of bug caused by this problem?

dump_request_write is only used for large size limit, I haven't found other case

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.

4 participants