-
Notifications
You must be signed in to change notification settings - Fork 998
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 server: fix last error reply #3728
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
why do we need this here? what are the cases that we ignore?
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.
Any error that has to do with parsing the arguments, unknown command etc -- we do the same in InvokeCmd. These are not interesting to us.
An example from a few lines below:
SendError
will register an error message for us to print but 1. it's not really interesting 2. it won't be printed at the right time.P.s. we do the same in InvokeCmd() for similar paths.
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.
what do you mean these are not interesting for us?
we want to see error messages for commands sent to dragonfly, so if we have problem we will know the command and the params sent and it will be easy to reproduce the problem and to know if this is bug on our side or on client side.
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.
Because those paths are not bugs related to commands, they are "soft errors". For example, acl authentication failed has nothing really interesting for us. The person could not execute the command because of their ACL's. If for some reason the client thinks that a command got rejected because of a bug they can file an issue. On the other hand, I most certainty don't think it would be useful to have a bunch of warnings because a client could not execute something that they have not credentials for. Similarly, for
VerifyCommandState
I don't think it's interesting let's say that a user could not run a command because the command is not allowed to be run under a script. These are soft errors and if we do have bugs, they can file the issue and it will be immediately apparent. Same applies for a command that gets rejected for arity (because the user did not specify enough arguments). I basically classify all of these errors are "soft" and I wanted to avoid logging them because even if there are bugs it will be easy to spot them. Furthermore, we log every second and that means that an ACL error will hide a command error and I believe the second is more important