You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow deleting a remote workroom while signed out of Codaset #285
🤖 Left by Claude Code, from the pre-landing review of #253.
RemoteWorkrooms.delete and deleteBase throw signedOut for any live host when there is no broker session (RemoteHosts.environment(toDelete:) needs BrokerSession.shared.client()). Removing the box itself needs only Docker, so a signed-out or expired session leaves remote workrooms that can't be deleted.
Possible approach: destroy the box without the broker, and keep the entry as failed with the live grant_id so a later delete (once signed in) cancels the grant. The grant is the only part that needs the broker.
Fixed by 7f7c6b8 (#309). Building the delete environment no longer needs a broker session, and RemoteProvisioning.tearDown now removes the box while signed out, leaving only the grant, which needs the broker to cancel. The entry is kept as failed with the live grant_id, so deleting it again once signed in cancels the grant. That is the approach this issue proposed. While signed out, the delete still reports an error for the grant, and no test covers the signed-out teardown path yet.
Activity
joelmoss commentedon Oct 3, 2026
🤖 Left by Claude Code
Fixed by 7f7c6b8 (#309). Building the delete environment no longer needs a broker session, and
RemoteProvisioning.tearDownnow removes the box while signed out, leaving only the grant, which needs the broker to cancel. The entry is kept asfailedwith the livegrant_id, so deleting it again once signed in cancels the grant. That is the approach this issue proposed. While signed out, the delete still reports an error for the grant, and no test covers the signed-out teardown path yet.