Add OUSD rebalancer to Talos schedules (manual, disabled)#2933
Merged
Conversation
Adds an `ousd_rebalancer` row to the Talos schedules seed so the OUSD Rebalancer action shows up in the Talos admin UI and can be triggered manually via "Run now". The hardhat task `ousdRebalancer` was already registered (and thus in the actions catalog), but with no `schedules` row it was neither listed nor runnable from the UI — the runner only dispatches by scheduleId (POST /runs/:scheduleId) and the ad-hoc arbitrary-command endpoint was removed. Seeded with enabled=false and the placeholder cron `0 0 1 1 *`, matching the existing manual-only rows (stake_validator, queue_proposal, ...), so it never fires on a schedule — only on an operator-initiated Run now. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
shahthepro
approved these changes
Jul 1, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2933 +/- ##
=======================================
Coverage 44.63% 44.63%
=======================================
Files 110 110
Lines 4920 4920
Branches 1362 1362
=======================================
Hits 2196 2196
Misses 2721 2721
Partials 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an
ousd_rebalancerrow tocontracts/migrations/seed_schedules.sqlso the OUSD Rebalancer action appears in the Talos admin UI and can be triggered manually via Run now.Why
The hardhat task
ousdRebalancer(tasks/actions/ousdRebalancer.ts) is already registered, so it shows up in the actions catalog (dump-actions-catalog.cjs→GET /actions/:task/params). But the catalog only advertises a task's editable flags — it does not make the action listed or runnable. The runner can only dispatch a run byscheduleId(POST /runs/:scheduleId,@talos/clienthttp.ts), and the ad-hoc arbitrary-command endpoint was removed. So without aschedulesrow, the rebalancer was neither visible nor executable from the UI.What
One row added, seeded with:
enabled = falseand the placeholder cron0 0 1 1 *— same convention as the other manual-only rows (stake_validator,remove_validator,queue_proposal,execute_proposal). It therefore never fires on a schedule; it only runs on an operator-initiated Run now.cd /app && pnpm hardhat ousdRebalancer --network mainnet(broadcasts, since the task'sdryrundefaults tofalse).The seed uses
INSERT ... ON CONFLICT (product, name) DO NOTHING, so it is idempotent and safe to re-apply on every runner boot.Notes
enabledtotruein the Talos admin UI (or update the cron here).🤖 Generated with Claude Code