Open gryan315 opened 3 years ago
The tool has just the harvester log at its disposal, when running a remote harvester. I checked, it simply does not have the req'd information. I think I will suppress the BLU/CYA discrimination by default, until the tool actually saw a farmer log entry. Once it sees that, it can claim to discern between them. No false pretensions.
So i have setup a few harvesters and a farmer/wallet that they repport to, i'm i understanding it correctly when i think that running this tool on the computer with the farmer/wallet won't work? That there is just not the correct info in the logs even with debug turned on? If not are there any other good solution when trying to keep track of multiple harvesters?
Sorry if i'm hijacking the thread, but it seem like the question sortof fitted the topic.
When using a remote harvester, the logs on that machine are significantly simplified compared to the logs on a full node machine:
On the full node I am getting the logs for partial proofs submitted by the harvester (no NFT plots on the full node):
One possible solution maybe: Have the full node create a cyan block when it sees a "submitting partial" with no accompanying "found n proofs"? Does anyone know if this new RPC harvester protocol will generate a new log line for a real proof found on the full node logs?