Under the hood
Useful2 Signal3
Transcript writes can go through a storage backend instead of plain files, but files remain the default.
What's wrong with this entry?
Anonymous. No account, no email.
What
Transcript appends, hydration, forking, snapshot copies, job timelines and history-suppression records all accept an optional storage backend and key. When one is supplied, writes go through that backend; with none supplied they fall back to a plain file append, which is what happens by default. Backend failures are re-shaped into standard errno-style errors so they show up in telemetry the same way file errors do.
Details
- Failure log line:
transcript storage append failed - Backend path uses append, replaceRecords and stat operations
Evidence
transcript storage append failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.