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

已關閉
TooManySugar3 年之前創建 · 1 條評論

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 在代碼提交 3 年之前 中引用了該問題
TooManySugar 評論 3 年之前'
所有者

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.
登入 才能加入這對話。
未選擇標籤
未選擇里程碑
未指派成員
1 參與者
正在加載...
取消
保存
尚未有任何內容