-
Notifications
You must be signed in to change notification settings - Fork 159
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
Reduce invalid job found log from error to warning #480
base: master
Are you sure you want to change the base?
Conversation
a rejected share seems slightly more important than INFO... maybe WARN? |
Yea - maybe warning. Most important is that we are consistent across all chip types. Mostly worried about these being misread as a serious issue (red-herring) when it is much more likely to be the symptom and not the cause, most of the time it is due to a mining.notify or connectivity instability. |
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.
Plz change to ESP_LOGW, otherwise LGTM
Updated |
While this message can be useful, most commonly it is seen after receiving a mining.notify, or briefly getting disconnected from the pool. changing it from a ERROR to WARNING log message to not scare users.
This also makes the implementation more consistent, as in some places and chips we already logged as ERROR and in other places as INFO.