fix: go to file in big non-git folders; linear reply handling

- find/git producers piped into head tolerate SIGPIPE, so hitting a cap no longer fails the command (and lets ttyd truncate its reply). - fs-find outside git skips build/cache folders and caps at 10000. - runCommand checks completion on the stream's tail instead of re-decoding the whole reply on every frame. Refs #37 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 01:50:50 -04:00
parent e345bf4640
commit dee1843986
5 changed files with 41 additions and 10 deletions
@@ -1,3 +1,14 @@
+devdesk (0.7.2) bookworm; urgency=medium
+
+  * Fix: Go to file failed in big non-git folders such as /root/code: the
+    file walk was cut off at its cap with SIGPIPE, which failed the command
+    and truncated its reply. Producers piped into a cap now tolerate it (also
+    for very large folders and git status). Outside git, Go to file skips
+    build/cache folders and stops at 10,000 files.
+  * Large side-channel replies no longer cost quadratic time in the browser.
+
+ -- Jared Vititoe <jjvititoe1@gmail.com>  Thu, 08 Oct 2026 01:50:50 -0400
+
 devdesk (0.7.1) bookworm; urgency=medium

  * Files pane reworked like VS Code (#37):