A cloud session that failed to start now shows the actual reason instead of a generic error.
tengu_linear_brook Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.251: off
Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When a cloud session is polled, for example under --print, a recorded startup failure is now raised as that specific error instead of the generic archived-or-errored response, so you see the actual reason the session never came up.
- gated on
tengu_linear_brook, which defaults to on in this build - with the flag off, polling falls back to the previous generic result
if (n.startupFailure && FNt()) throw T(n.startupFailure);
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
A whitespace-only prompt gets its own error
Both mention print
-
v2.1.242
--printwith--cloudcan message an existing cloud sessionBoth mention print
-
v2.1.239
One shared test for whether a run is headless
Both mention print