We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a new 2.5 reward cycle starts and the aggregate key isn't set, the signer has this log every few seconds:
Signer #N: Could not lookup current miner while in active reward cycle
I thought we'd removed this log during 2.5, but looks like we haven't.
Relates to:
The text was updated successfully, but these errors were encountered:
#4760
@hstove is it feasible to have a PR addressing this for next week?
Sorry, something went wrong.
Fixed by #4768
Successfully merging a pull request may close this issue.
When a new 2.5 reward cycle starts and the aggregate key isn't set, the signer has this log every few seconds:
I thought we'd removed this log during 2.5, but looks like we haven't.
Relates to:
The text was updated successfully, but these errors were encountered: