t1405: Fix HIGH quality-debt in setup.sh from PR #2936 review#2963
t1405: Fix HIGH quality-debt in setup.sh from PR #2936 review#2963marcusquinn wants to merge 1 commit intomainfrom
Conversation
…etup.sh Address 4 findings from PR #2936 review (GH#2950): - HIGH: Remove 2>/dev/null from cmd_set calls (lines 815, 821) so users see errors when consent persistence fails instead of being silently re-prompted on next run. The || true still prevents set -e exits. - MEDIUM: Remove 2>/dev/null from grep on legacy config (line 773) since file existence is already checked on line 771 — suppressing stderr masks permission errors, not missing-file errors. - MEDIUM: Single-quote variable expansions in crontab entry (line 924) to prevent command injection via directory names containing shell metacharacters.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Fri Mar 6 02:54:06 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
|
This PR appears orphaned — no active worker process found and no activity for 6+ hours. Flagging for re-dispatch. If work is still in progress, remove the |



Summary
2>/dev/nullfromcmd_setcalls (lines 815, 821) so users see errors when consent persistence fails — prevents silent re-prompting on next run2>/dev/nullfromgrepon legacy config (line 773) where file existence is already verified — suppressing stderr masks permission errorsDetails
Addresses all 4 findings from Gemini code review on PR #2936:
cmd_setconsent persistencegrep+ command injection in crontabShellCheck passes clean.
Closes #2950