Skip to content

fix: print zip truncation warning unconditionally to stderr#69

Merged
claude[bot] merged 1 commit intomainfrom
claude/issue-64-20260227-0823
Feb 27, 2026
Merged

fix: print zip truncation warning unconditionally to stderr#69
claude[bot] merged 1 commit intomainfrom
claude/issue-64-20260227-0823

Conversation

@claude
Copy link
Contributor

@claude claude bot commented Feb 27, 2026

When a repository exceeds the 10 MB zip limit, the truncation warning was routed through logFn, which is a no-op in non-debug mode. Users on large repos silently received incomplete graph analysis with no indication that truncation had occurred.

Changes

  • cmd/run.go (runHandler): Changed the truncation warning from logFn(...) to fmt.Fprintf(os.Stderr, ...) so it always prints.
  • cmd/run.go (runWithoutCache): Same fix applied to the second occurrence of the truncation warning.

Fixes #64

Generated with Claude Code

Previously the truncation warning was routed through logFn, which is a
no-op in non-debug mode. Users on large repos silently received incomplete
graph analysis with no indication truncation had occurred.

Fixes #64

Co-Authored-By: Grey Newell <greyshipscode@gmail.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@claude claude bot merged commit f49244f into main Feb 27, 2026
1 check passed
@claude claude bot deleted the claude/issue-64-20260227-0823 branch February 27, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: repo zip truncation warning is silently swallowed in non-debug mode

0 participants