If a folder is too big to seed a cloud session, you now see the size, cap and biggest files.
tengu_ccr_bundle_seed_enabled Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.246: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.246. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When a folder is too big to seed a cloud session, the refusal now lists the total size, the limit, and the biggest files, and points out that a .gitignore in the folder is respected so you can exclude what the session does not need.
- A separate branch covers folders holding more files than a session can start with.
- A third refusal lists files that changed while they were being read.
- Same switch as folder seeding:
CCR_ENABLE_BUNDLEor the remotetengu_ccr_bundle_seed_enabled.
Remove or ignore what the session does not need (a .gitignore in this folder is honoured) and start again
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Cloud seeding tells you when there are too many untracked files
Both mention gitignore