Closed teslashibe closed 4 months ago
In order to test the accumlatedUptime fixes in test we need to remove old nodeData that shows accumulatedUptime out of bounds.
{ "multiaddrs": [ "/ip4/171.239.188.121/udp/52571/quic-v1" ], "peerId": "16Uiu2HAm9P1PDBVktwivMPrT839zWNFdX9hyJ7VYmshrTsutrcus", "firstJoined": 1721298246, "lastJoined": 1721298246, "lastUpdated": 1721320723, "uptime": 557062033724000, "uptimeStr": "6 days 10 hours 44 minutes", "accumulatedUptime": 231235215726125105, "accumulatedUptimeStr": "2676 days 8 hours 0 minutes", "ethAddress": "0x45161D2799A089Ea1f27A52DFBbB614F4b0c17c6", "isActive": true, "isStaked": false, "isValidator": false, "isTwitterScraper": false, "isDiscordScraper": false, "isWebScraper": false, "version": "0.5.0" }
awesome-masa
This is done automatically on release, closing it
In order to test the accumlatedUptime fixes in test we need to remove old nodeData that shows accumulatedUptime out of bounds.
For example:
Acceptance criteria
awesome-masa
repo to check nodes out of bounds within 2hrs, 12hrs, 24hrs, 48hr, 72hrs