fix: duplicated memory guard — memory_guard() in env.sh vs check_memory() in formula-session.sh #279
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Two implementations of memory checking:
dev-agent.sh, dev-poll.sh, review-pr.sh call memory_guard(). All *-run.sh scripts call check_memory(). They parse memory differently and could disagree on available memory.
Fix
Remove check_memory() from formula-session.sh. Update all *-run.sh scripts to call memory_guard() from env.sh (already sourced by all scripts). memory_guard() reads /proc/meminfo which is more portable (doesn't require procps/free).
Affected files
Acceptance criteria