I had a bit of downtime recently and was again using the earnings.py, and found some minor issues, that forced me to change the code ever so slightly to get the information i needed.
this node isnât vetted on one satellite, and since one of the recommended ways to check if a node is vetted and that it takes 30 days for downtime to drop, then when one has downtimes the % vetted information gets dropped from the print out.
oh wait works fine that way⌠thought this was both ways but apparently itâs only when the node is already vetted and downtime is above 2%
looks like this with current code, and latest version of earnings.py
and if i change the allowed downtime before the warning to 10% then i can see that the node is infact vetted to that particular satellite.
talking about us2 in case there was any doubtâŚ
i know that one essentially could figure this out, because it will only show the warning without the % vetted information, if it has already finished vetting on the satellite in question.
this however requires previous knowledge about how earnings.py works.
thus i suggest changing , so that the vetting OK status be added âŚ
i guess adding an OK status to a warning is kinda a bad ideaâŚ
maybe just keep vetted % after the warnings, even if at 100%
also seems to affect all the warnings from what i can see in the code⌠but donât really know python⌠so, its a bit of an assumption.
i duno what the best solution is for the problem, but i figured you wanted me to point out the issue.
might be useful for other new people which wonât have prior knowledge and will be vetting nodes⌠so i figured a modification of earnings.py made sense.
and it takes an aweful long time for downtime to go away ofc⌠so its not like its a fleeting issue.