-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] Impossible farmer response time for unfinished_blocks on SP: 0 in full_node logs #11869
Comments
Same on 1.3.5 |
I can confirm on my node on Windows with Chia 1,3,5 2022-06-10T23:05:23.165 full_node chia.full_node.full_node: INFO Added unfinished_block e946364b1a6749de50ae624fb73cba97f1368354ea6789e00a699ce88ecf6822, not farmed by us, SP: 0 farmer response time: 3798.2807, Pool pk xch1yp8tqnnsjrttdtnrqftr4d3fsrrj58pxgegspmsyc0kkny3vwuuqgwc36t, validation time: 0.0156 seconds, pre_validation time 0.0312, cost: 420761575, percent full: 3.825% |
There is a bug with SP 0 as it's not a signage point like the others, it's a special end of slot condition and so needs some other code. But this is strictly a logging bug and doesn't affect anything else. |
Fixed in 1.6.2 by #136555 |
What happened?
With info level logs running on a full node, the "Added unfinished block" entry will periodically provide an impossible number for "farmer response time" on entries for SP: 0. This can be seen either by parsing for results that are greater than a reasonable number of seconds (almost always returning a SP: 0 entry) or by specifically parsing for SP: 0 entries.
for example:
cat ~/.chia/mainnet/log/debug.log.1 ~/.chia/mainnet/log/debug.log | tr -d ',' | awk '/farmer response time/ {if (2000 < $17) {print}}'
will likely return every single SP: 0 entry from the latest 2 log files.Version
1.2.11
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
The text was updated successfully, but these errors were encountered: