-
Notifications
You must be signed in to change notification settings - Fork 312
Closed
Labels
Description
Objective
Fix a systemic bug in the push_repo_memory tool where it reports a false-positive size limit error, blocking workflows from storing memory even when actual files are tiny.
Context
From the Daily Audit Report (discussion #22237):
push_repo_memoryreports 'Total memory size (30 KB) exceeds allowed limit of 12 KB' even though actual files total only ~500 bytes. Appears to measure something other than working tree file sizes (possibly git pack size or global repo size).
This bug has been observed in multiple workflows:
- PR Triage Agent (run §23391811735)
- The Audit Agent itself (actual files: ~560 bytes, reported size: 29 KB)
This is a recurring systemic issue — not a one-off. The tool is likely measuring git object store / pack size rather than the working tree file sizes.
Investigation Steps
- Locate the
push_repo_memorytool implementation (likely inactions/setup/js/orpkg/) - Find the size calculation logic — identify what is actually being measured
- Confirm hypothesis: is it measuring git pack/object store size instead of working tree files?
- Fix the size calculation to measure actual working tree file sizes only
Files to Investigate
actions/setup/js/— JavaScript action files (likely containspush_repo_memory)pkg/— Go source (if tool logic lives here)- Look for size limit constant (12 KB limit) and the measurement code
Acceptance Criteria
- Root cause identified and documented
- Size calculation measures actual working tree files (not git internals)
- Workflows with <12 KB of actual memory files no longer hit false-positive limit errors
- Existing tests pass (
make agent-finish)
Generated by Plan Command for issue #discussion #22237 · ◷
- expires on Mar 24, 2026, 8:48 AM UTC
Reactions are currently unavailable
Metadata
Metadata
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.