When a session transcript won't load, you're told exactly why in plain words.
What's wrong with this entry?
When a session transcript cannot be read, the error says why in plain words: the file is a symbolic link, something other than a regular file is in its place, it exceeds the size limits, or it changed while being read, in which case you are told to run the command again.
- Replaces raw filesystem error codes in the session load path.
- Symlinked transcripts are reported as unsupported rather than silently followed.
this session's transcript is a symbolic link, which session storage does not read through.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.