fix: restore gateways to active set after long inactivity#202
fix: restore gateways to active set after long inactivity#202
Conversation
|
🚀 Subgraph Studio preview deployed
curl -H 'Content-Type: application/json' \
-d '{"query":"{ protocol(id: \"0\") { inflation } }"}' \
https://api.studio.thegraph.com/query/31909/livepeer-ci/pr-202-b67dbc4-20964667423 |
Ensure gateways which were inactive for >90 days are added to the active set again so 30/60/90-day fee sums update.
ce0d65d to
cc648fd
Compare
|
This should have been already done in: Line 197 in cc648fd Not sure why it was not working without this logic. |
I identified the issue: it was caused by creating and persisting two separate protocol objects. I removed the logic from the This introduces some ambiguity around I opened #210 to track this and create a follow up pull request. |
9d3a794 to
ac5fae4
Compare
Move active broadcaster updates into `winningTicketRedeemed` to avoid stale protocol saves and ensure inactive gateways rejoin the active set for rolling fee totals.
ac5fae4 to
acfdddd
Compare
Description
Ensure gateways which were inactive for >90 days are added to the active
set again so 30/60/90-day fee sums update.
Fixes # (issue)
Checklist
yarn prepareand verifiedyarn codegenandyarn buildsucceed.yarn deploy:local.