Skip to content

refactor(kaspa): remove max attempts from migration retry loops#451

Merged
danwt merged 3 commits intomain-dymfrom
danwt/claude/fix-migration-trace-null-payload
Jan 23, 2026
Merged

refactor(kaspa): remove max attempts from migration retry loops#451
danwt merged 3 commits intomain-dymfrom
danwt/claude/fix-migration-trace-null-payload

Conversation

@danwt
Copy link
Copy Markdown

@danwt danwt commented Jan 23, 2026

Summary

  • Migration and hub sync now retry indefinitely instead of failing after 10 attempts
  • Appropriate for an unattended process that must eventually succeed
  • Removes MAX_ATTEMPTS constant and simplifies control flow

Test plan

  • Compiles cleanly
  • Deploy on blumbus and verify migration completes with indefinite retries

🤖 Generated with Claude Code

danwt and others added 3 commits January 23, 2026 15:14
Migration transactions have no payload (no withdrawals processed),
but the trace function required a non-null payload. Treat null as
empty — no message IDs to extract.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Same issue as relayer trace — validators also reject null payload
with MissingTransactionPayload. Treat null as empty MessageIDs.
Remove unused MissingTransactionPayload error variant.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Migration and hub sync now retry indefinitely instead of failing after
10 attempts. This is appropriate for an unattended process that must
eventually succeed.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@danwt danwt merged commit cb28cfc into main-dym Jan 23, 2026
7 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant