You'll notice
Useful3 Signal2
Unusual git checkouts fall back to the older upload path instead of blocking your cloud session.
What's wrong with this entry?
Anonymous. No account, no email.
What
Cloud sessions could refuse to start on checkouts the new hardened upload path cannot handle. Those layouts now fall back to the previous upload method for that session, with a warning, instead of failing.
Details
- Layouts classified as unsupported: a
.gitfile instead of a directory, a separate work tree, included config, many includes, an old git version, borrowed objects, reftable, and partial clones on old git. - Reported as
fallback_eligibleintengu_ccr_bundle_upload. - The warning also notes the legacy path uploads uncommitted files with credential-like names that the new path holds back.
- When hardening is explicitly required for device sessions, the old hard failure still applies.
Evidence
the new upload path does not support that yet, so the working tree is being uploaded the previous way for this session.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.