Skip to content

FLO-27: non-panicking fixReschedule with stale UUID self-cleanup#207

Open
holyfuchs wants to merge 2 commits intomainfrom
holyfuchs/FLO-27-stale-supervisor-uuid
Open

FLO-27: non-panicking fixReschedule with stale UUID self-cleanup#207
holyfuchs wants to merge 2 commits intomainfrom
holyfuchs/FLO-27-stale-supervisor-uuid

Conversation

@holyfuchs
Copy link
Member

@holyfuchs holyfuchs commented Mar 5, 2026

Closes: #236

  • FlowALPRebalancerPaidv1.fixReschedule(uuid:) returned Void and force-unwrapped borrowRebalancer(uuid)!. A stale UUID (rebalancer deleted without removing from the Supervisor set) caused a panic, reverting the entire executeTransaction and blocking recovery for all other paid rebalancers in that run.
  • fixReschedule now returns Bool — true if the rebalancer was found and processed, false if the UUID no longer exists.
  • The Supervisor's executeTransaction loop checks the return value; on false it calls removePaidRebalancer to self-clean the stale entry, so subsequent ticks are not affected.

@holyfuchs holyfuchs requested a review from a team as a code owner March 5, 2026 15:56
@liobrasil
Copy link
Contributor

closes #236

@holyfuchs holyfuchs changed the title fix(FLO-27): non-panicking fixReschedule with stale UUID self-cleanup FLO-27: non-panicking fixReschedule with stale UUID self-cleanup Mar 6, 2026
@holyfuchs holyfuchs force-pushed the holyfuchs/FLO-27-stale-supervisor-uuid branch from c7a0dc3 to 769b8c2 Compare March 6, 2026 11:22
Co-authored-by: Bastian Müller <bastian@turbolent.com>
@holyfuchs holyfuchs force-pushed the holyfuchs/FLO-27-stale-supervisor-uuid branch from 769b8c2 to 68dd1aa Compare March 6, 2026 12:41
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.

FLO-27: Stale Supervisor Uuid Bricks Recovery Calls

4 participants