-
Notifications
You must be signed in to change notification settings - Fork 473
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
Return an error when Stream::Range fails and remove some debug server logs #1556
Conversation
ee4dc70
to
cf80ff7
Compare
@xiaobiaozhao Why force push cf80ff7? |
rebase ? |
It is very weird. DO NOT force push to other contributor's branch without notification. If you want to merge unstable to it, just click the "Update Branch" button, it will append a new commit. |
@xiaobiaozhao And I would like to state that I believe this is a very serious violation of the "unspoken agreement" among committers in git operations. |
Yes, you can append a new commit and SHOULD NOT rebase or force push to other contributors' PR. |
OK, got it |
These logs were there in the earliest days, i guess they are for debug, remove them now to avoid polluting the server logs. The blpop one is easy to reproduce: ``` Failed to execute redis command: blpop, err: Invalid argument: WRONGTYPE Operation against a key holding the wrong kind of value ``` Checked the relevant LOG calls and fix a typo.
cf80ff7
to
8876d60
Compare
i doing a force-push since it is a trivial diff. |
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
Thanks all, merging... |
… logs (apache#1556) This PR has two parts. The first one, internally, both XREAD and XRANGE call the Stream::Range function. When Range fails, we should return an error. The second one is to remove the debug logs. These logs were there in the earliest days, I guess they are for debugging, remove them now to avoid polluting the server logs. The blpop one is easy to reproduce: ``` Failed to execute redis command: blpop, err: Invalid argument: WRONGTYPE Operation against a key holding the wrong kind of value ```
… logs (#1556) This PR has two parts. The first one, internally, both XREAD and XRANGE call the Stream::Range function. When Range fails, we should return an error. The second one is to remove the debug logs. These logs were there in the earliest days, I guess they are for debugging, remove them now to avoid polluting the server logs. The blpop one is easy to reproduce: ``` Failed to execute redis command: blpop, err: Invalid argument: WRONGTYPE Operation against a key holding the wrong kind of value ```
… logs (apache#1556) This PR has two parts. The first one, internally, both XREAD and XRANGE call the Stream::Range function. When Range fails, we should return an error. The second one is to remove the debug logs. These logs were there in the earliest days, I guess they are for debugging, remove them now to avoid polluting the server logs. The blpop one is easy to reproduce: ``` Failed to execute redis command: blpop, err: Invalid argument: WRONGTYPE Operation against a key holding the wrong kind of value ```
This PR has two parts.
The first one, internally, both XREAD and XRANGE call the Stream::Range
function. When Range fails, we should return an error.
The second one is to remove the debug logs. These logs were there in the
earliest days, i guess they are for debug, remove them now to avoid polluting
the server logs.
The blpop one is easy to reproduce:
Checked the relevant LOG calls and fix a typo.