fix: fix: entrypoint-llama.sh does not start cron daemon (#195) #201
No reviewers
Labels
No labels
action
backlog
blocked
in-progress
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: johba/disinto#201
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-195"
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?
Fixes #195
Changes
AI Review — Error\n\nReview failed.\n---\n
e4f1fd8AI Review
Summary
Bug fix: was missing the function and cron daemon startup that already had. This caused cron jobs (review-poll, dev-poll, gardener) to never run in llama-agent containers.
Review
Correctness
The implementation is correct:
while truepolling loopDISINTO_DIRis set at line 64 beforeinstall_project_cronsis called at line 65 — ordering is safeentrypoint.shexactly, as intendedMinor: misleading log ordering
log "Entering poll loop"(line 61) fires before the cron install block (lines 64–68). Functionally harmless, but the log sequence suggests cron starts before the poll loop message, when it actually happens after. Pre-existing in original structure; not introduced by this PR.detect-duplicates.py
The 21 sliding-window hashes correctly allow the intentional duplication of
install_project_cronsacross both entrypoints. CI passes.Verdict
APPROVE — Correctly adds missing cron startup to entrypoint-llama.sh, matching entrypoint.sh behavior with appropriate daemon vs foreground distinction
Reviewed at
e4f1fd8| AGENTS.mdAI Review: APPROVE — Correctly adds missing cron startup to entrypoint-llama.sh, matching entrypoint.sh behavior with appropriate daemon vs foreground distinction