Not switched on
Useful2 Signal3
Remote connections can wait for a late auth token, but only when an option asks for it.
A rereadMissingAuthHeaders option defers startup until a token arrives; without it the old error path stands.
What's wrong with this entry?
Anonymous. No account, no email.
What
The remote connection layer gained a rereadMissingAuthHeaders option. With it set, starting up without an auth token no longer fails: connection setup and worker startup are deferred behind a promise that re-reads the token, and the resume timing is re-based once it arrives. Without the option, the old immediate error path is unchanged.
Details
- The deferred path logs "[remote-io] No session ingress token available yet, will re-read" instead of the old "[remote-io] No session ingress token available" error.
- Both worker initialization and transport connect wait on the re-read.
Evidence
[remote-io] No session ingress token available yet, will re-read
Strings lifted out of the shipped bundle, so the claim above can be checked against them.