You'll notice
Useful2 Signal2
Background sessions that hit an already-claimed session id now fail with a clear dimmed notice.
What's wrong with this entry?
Anonymous. No account, no email.
What
If a background session starts with an id another session already claims, it now ends on its own path: the session is marked crashed, a dimmed notice goes to the output stream, and a dedicated event is recorded with the attempt number, how it was launched and the launch mode. Previously this fell into the generic crash and exit handling.
Details
- Event name
tengu_bg_session_id_taken, withattempt,viaandlaunch_modefields. - Unconditional on this code path; no flag.
Evidence
tengu_bg_session_id_taken
Strings lifted out of the shipped bundle, so the claim above can be checked against them.