Skip to content

Prevent duplicate instance launches and surface starting/terminating states in UI#239

Open
D-VR wants to merge 1 commit intoctfer-io:mainfrom
D-VR:better-UI-instance-handling
Open

Prevent duplicate instance launches and surface starting/terminating states in UI#239
D-VR wants to merge 1 commit intoctfer-io:mainfrom
D-VR:better-UI-instance-handling

Conversation

@D-VR
Copy link
Contributor

@D-VR D-VR commented Nov 24, 2025

  • Add a non-blocking player lock when creating instances so a second POST immediately returns 409 "already starting or running" instead of hanging.
  • Persist a "starting..." state in the challenge view (survives refresh) to disable the launch button and show meaningful feedback while provisioning.
  • Detect instances that have expired but still exist (cron cleanup pending) by checking since + until < now, show "terminating..." and disable launch until cleanup finishes (i.e. cleanup finishes when the instance no longer exists, i.e. 404).

Issues: Addresses #231 and improves user-facing errors for the scenarios discussed in #225, this closes #232

@NicoFgrx NicoFgrx force-pushed the better-UI-instance-handling branch from c97e97b to 76bd969 Compare January 7, 2026 16:49
@NicoFgrx
Copy link
Member

Hi, I tried to integrate the PR, but it’s not working (or maybe I don’t understand what it’s supposed to do).
From what I gather, when I start creating an instance, the "Starting..." button should remain visible even after closing the pop-up, but that’s not happening.

Any idea what might be causing this?
P.S. I synced the branch with your repo to include the latest upstream main project changes.

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.

[Bug]: Web UI does not show challenge as starting

2 participants