-
Notifications
You must be signed in to change notification settings - Fork 26
Fix crashes caused due race condition. #52
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
Conversation
…to be the main cause miner dont appear hashing on pool
… loop, same for current
| if (millis() - current_last_hash > 200000) | ||
| if (millis() - current_last_hash > 600000) | ||
| { | ||
| l_error(TAG_CURRENT, "No hash received in the last 3 minutes. Restarting..."); |
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.
@KillerInk 10min waiting is not too much?
If fine, worth update the error with the proper amount of time
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.
no its fine. pool.io increase diff to 0.001 and there can be hashtimes longer then 5min where also no new job trigger.
and after 10min then min there should be latest a new job request(new block). if not ,connection realy died.
matteocrippa
left a comment
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.
Thanks for the contribution @KillerInk
Idrop just a minor comment

Description
Scope of the commit
Unit test
Dependencies and Compatibility
AsyncTcp
Documentation
Breaking Changes
miner works without crashing.
optimise send and request with asynctcp
fix timings on job change.
add support for seedstudio xiao s3
Additional Checks
Contributor Guidelines