Skip to content

connect, cli: select cloud routing after authentication - #8

Merged
karalabe merged 1 commit into
dark-bio:mainfrom
karalabe:fix-windows-reconnect
Sep 15, 2026
Merged

karalabe merged 1 commit into
dark-bio:mainfrom
karalabe:fix-windows-reconnect

Conversation

@karalabe

@karalabe karalabe commented Sep 15, 2026

Copy link
Copy Markdown
Member

Connecting to a develop or staging hardware Ark without --env first opened it with release routing, then closed and immediately reopened USB after attestation. Windows could reject that second open with error 5 while the original handle was still being released.

Select cloud routing from the authenticated identity before starting cloud services, keeping the original connection. Environment precedence remains --env, attestation, launcher metadata, then release. Regression tests cover routing after authentication, rejection before routing, and attested hardware without launcher metadata.

Fixes #6.

Connecting to a develop or staging Ark without --env reopened its USB
connection after attestation. On Windows, the second open could fail with
access denied while the first handle was still being released.

Select the cloud route from the authenticated identity before starting
cloud services, keeping the original session and existing environment
precedence. Cover routing after authentication and rejection before routing.

Fixes dark-bio#6

Co-authored-by: Codex <noreply@openai.com>
@karalabe
karalabe merged commit db2cd0a into dark-bio:main Sep 15, 2026
8 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.

Cannot connect on Windows 💩

1 participant