Bug Report: `events.jsonl` gets too big and fills up disk space
- Dominant language
- Shell
- Stars
- 437
- Forks
- 32
- Avg merge
- 4h 43m
- Merged PRs (30d)
- 7
Description
### Description
When a script runs for a long time and prints a lot of text to the console, Junie saves all of that output into the session's log file (`events.jsonl`).
There is currently no limit on how large this file can get. In a recent run, a script printed so much text that the file grew to **459 GB** in a few hours, completely filling up the hard drive.
### Screenshots
### Expected Behavior
The app should stop the log file from taking over the computer's storage by:
* Setting a maximum size limit for the log file.
* Deleting old text or rotating files when they get too big.
* Slowing down or pausing if a script prints too much text too quickly.
### Actual Behavior
The app keeps writing every line of text to the file until the computer completely runs out of disk space.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the session logging path that writes events.jsonl, then reproduce the issue with a long-running script that emits substantial console output. Done means the log cannot exhaust the disk and the selected size, rotation, throttling, or cleanup behavior is covered by tests; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100