You'll notice
Useful3 Signal3
Cloud session disconnects and skipped files now name a cause and a next step.
What's wrong with this entry?
Anonymous. No account, no email.
What
Cloud session failures now name a cause and a next step instead of failing quietly. Disconnects distinguish the stream closing, an untrusted device, a stale session needing a fresh sign-in on this machine, and a rejected attach, and creation failures cover a session that was made but could not be bound to this machine. The separate list of local files that were not sent to a cloud session was rewritten in the same pass, so each exclusion says which file it is about and why.
Details
- Disconnect and creation messages carry what to do, usually re-signing in on this machine or starting a new session because the old one may have been archived.
- Creation failures say whether the unbindable session was archived afterwards.
- Session ids are truncated and hashed in these messages, so an id beginning
cse_is reported assession_<hash>. - The file exclusion list leads with settings that failed to parse, which leaves your Read permission rules unknown, and points you at
/status. - Git filter exclusions name LFS and git-crypt as examples.
- Read rules set to deny or ask are described as covering the specific file rather than in general terms.
Evidence
Cloud session disconnected, a git filter (LFS, git-crypt) applies to
Strings lifted out of the shipped bundle, so the claim above can be checked against them.