Conversation
Rotates the log file at 10MB, keeping one .old backup. This prevents the hook log from consuming excessive disk space over time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
prism-hooks.logfile had no size limits and grew to 979MB on one machine, consuming significant disk space with no rotation or cleanup.This adds simple log rotation: before each write, if the log exceeds 10MB, it is renamed to
prism-hooks.log.old(replacing any previous backup), and a fresh log is started. This caps disk usage at ~20MB (current + one rotated backup).Changes
prism-hooks.logat 10MB, keeping one.oldbackupTest plan
go buildandgo vetpass🤖 Generated with Claude Code