[BUG] Endless scrolling after large test output
Resolved 💬 10 comments Opened Apr 20, 2025 by Cheffromspace Closed Jan 12, 2026
- System Environment:
- Running in WSL2 on Windows (Ubuntu 22.04.5 LTS)
- Linux kernel 5.15.133.1-microsoft-standard-WSL2
- Using zsh shell with TERM=xterm-256color
- Claude version: 0.2.74 (Claude Code)
- Project Environment:
- Node.js v20.15.1
- PNPM v9.14.4 (package manager)
- Large project with many dependencies
- Using Jest v29.7.0 for testing
- Events Leading to Issue:
- We were running Jest tests with a command like: pnpm test "src/commands/slashCommand.test.ts"
- The test was failing and producing extremely large error output
- Specifically, the test was logging a full API response from a pollution API that was being truncated at 28,000+ characters
- Notable Observations:
- The test file (slashConnamd.test.ts) has 307 lines
- The npm/pnpm dependency tree shows some conflicts/issues with Jest dependencies
- There's plenty of system resources available (memory: 96GB with ~90GB free)
- The WSL filesystem is mounted to Windows drives, which could potentially cause I/O issues
- Potential Causes:
- Terminal buffer overflow due to extremely large error output
- Special characters or ANSI escape sequences in the error output affecting terminal rendering
- Interaction between Windows Terminal and WSL
- Possible issues with Jest's output formatting when running in WSL
The most likely cause appears to be the extremely large error output from the failing test, which contained the full API response data (28,000+ characters) being repeatedly logged to the terminal, possibly overwhelming the terminal's buffer or rendering capabilities.
https://github.com/user-attachments/assets/86040c0c-1388-4ced-9905-be8df81c9048
This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗