-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improve CECP-compliance of error-reporting #10
Comments
At the moment have no other ideas for the improvements. Perhaps the board-printing chatter is better off to be removed altogether unless compiled with special debug flags -- but those are done as CECP comments, so should not affect any functionality negatively. |
This error reporting change seems to have helped with Arena engine autodetection -- not a recommended way to set up engines there, but nevertheless available and apparently used by some people. Key point seems to be that after receiving Sample log from Linux Arena 3.10beta
|
Threads on Arena autodetection: |
Announce errors with prefix, optional description and command name
As leftover from console-only interface 'Unrecognized command' is sent also when speaking CECP
However, most compatible way of CECP is:
given earlier situation, that would be e.g.:
Error (Unrecognized command): dafadsfds
orError: dafadsfds
orError (unknown command): dafadsfds
, etcVerify robust command argument parsing
E.g.
to_int
is used for CECPsd
argument parsing and when given in succession, this fails with conversion error announced.Expected behaviour would be to announce unknown command error in the same format as described before, e.g:
Error (unknown command): sdf
Similarly for other imaginable happenings likestx
, etc.The text was updated successfully, but these errors were encountered: