Snapshot patch can produce multi-MB parts with 100K+ file entries #18921

Activity

1. github-actions

   assigned

   thdxr

   on Mar 24, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Mar 24, 2026
3. github-actions commented on Mar 24, 2026

   

   github-actionsBot

   on Mar 24, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887: Also about the snapshot system tracking/processing files it shouldn't (large unignored directories) — similar root cause around unbounded file handling in snapshots, though the specific mechanism differs (this issue is about git diff --name-only in Snapshot.patch(), while [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887 is about git add in Snapshot.track()).
   • Warn or block snapshots when the detected git root is an accidental top-level repo #18857: Related — about the snapshot system operating on unexpectedly large git worktrees with many files.

   If your issue is specifically about the patch part size from Snapshot.patch(), it may be a new and distinct problem worth tracking separately.
4. thdxr

   assigned

   kitlangton

   and unassigned

   thdxr

   on Apr 26, 2026
5. thdxr

   removed

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on May 3, 2026
6. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
7. github-actions

   closed this as not plannedon Jul 3, 2026