#1 Spamming "Worker not reset on payout" after payout and actual reset

Closed
opened 3 years ago by TooManySugar · 1 comments

Check update_data:
https://gogs.veloe.link/TooManySugar/GoEthemineTelegramBot/src/69f25124457b342a9a9ef0696bee460bbbbdfff7/update_data.go#L258
Most likely compares time to self time. Due to logic diff of cs entity and gorm

Check update_data:<br> https://gogs.veloe.link/TooManySugar/GoEthemineTelegramBot/src/69f25124457b342a9a9ef0696bee460bbbbdfff7/update_data.go#L258<br> Most likely compares time to self time. Due to logic diff of cs entity and gorm
TooManySugar referenced this issue from a commit 3 years ago
TooManySugar commented 3 years ago
Owner

Fixed in 4f294e09f2
Problem was in a time differences at given by pool api stats for miners/workers and payouts. It is possible to get payout`s time higher then updated time of miners/workers and then this issue occurs: so at update with payout would be written right up to date entry. Which will be considered an error in the next update.
Fix was to do actual check is it's zeroed or not if it's time less then last payout's time.

Fixed in 4f294e09f2<br> Problem was in a time differences at given by pool api stats for miners/workers and payouts. It is possible to get payout`s time higher then updated time of miners/workers and then this issue occurs: so at update with payout would be written right up to date entry. Which will be considered an error in the next update.<br> Fix was to do *actual* check is it's zeroed or not if it's time less then last payout's time.
Sign in to join this conversation.
No Label
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.