-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add slot_index property to signers #46
Conversation
Vercel deployment URL: https://signer-metrics-o8d4jit2k-hirosystems.vercel.app 🚀 |
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
## [0.8.0](v0.7.0...v0.8.0) (2024-11-08) ### Features * add slot_index property to signers ([#46](#46)) ([79e399a](79e399a))
🎉 This PR is included in version 0.8.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
pgm.dropIndex('reward_set_signers', ['block_height']); | ||
pgm.dropIndex('reward_set_signers', ['cycle_number']); | ||
pgm.dropConstraint('reward_set_signers', 'reward_set_signers_cycle_unique'); | ||
pgm.renameTable('reward_set_signers', 'reward_set_signers_old-no-slot-index'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping the table for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
Closes #40
The sql migration just drops the current table to trigger the existing runtime logic which will detect missing cycle signer sets, fetch them, and insert them (this time with the slot_index data). This is cleaner and less error-prone than an alter-table migration + missing slot_index detection + table updating logic.