{"version":"2.1.248","anchor":"snapshots-report-when-there-are-too-many-changed-paths-to-li","canonical_anchor":"snapshots-report-when-there-are-too-many-changed-paths-to-li","heading":"Snapshots report when there are too many changed paths to list","tier":"notice","area":"Checkpoints","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/snapshots-report-when-there-are-too-many-changed-paths-to-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Snapshots report when there are too many changed paths to list\n\nCheckpoint snapshots of huge trees now say there were too many paths instead of half-finishing.\n\n**What**\n\nA checkpoint snapshot of a very large working tree can now stop with a clear message instead of producing an incomplete result, and deleted files are counted in the snapshot's path total.\n\n**Details**\n\n- Attribute listing can return an overflow result, surfaced to you as reason `too_many_paths` with a message saying the attribute listing overflowed; overflowed entries are dropped from the collected list.\n- Deletions are no longer folded into the bulk staging call; absent paths are listed explicitly from the index instead.\n- Files marked skip-worktree are un-marked before being re-added.\n- The reported `stats.paths` count now covers removed paths as well as staged ones.\n\n**Evidence**\n\n`more changed paths than a snapshot can list (the attribute listing overflowed)`\n\n- Area: Checkpoints\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}