Claude/cpu guard script dn d8u

[gamblecodezcom]

Summary by Sourcery

Aggressively clear port conflicts before and after restart, simplify post-start health checks and Telegram reporting, and harden filesystem operations and permissions for logs, QA artifacts, and editor saves.

Enhancements:

• Add a dedicated helper to kill processes squatting on the bot port and use it before restart and during auto-recovery.
• Streamline post-start health check logic into a single-pass flow with bounded retries and a concise Telegram deployment report including recent logs.
• Tighten file permissions and options for admin logs, QA artifacts, atomic writes, and SSH editor saves, and centralize QA filesystem error suppression with more robust logging.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sourcery-ai]

Reviewer's Guide

Harden pre-/post-start health and port conflict handling in prod-run.sh, simplify and centralize QA filesystem error handling and permissions in index.js, and tighten file modes for various logs and artifacts.

Sequence diagram for aggressive pre-start port conflict clearing

sequenceDiagram
    participant ProdRunner as prod_run_sh
    participant PortCheck as is_port_listening
    participant Killer as _kill_port_squatters
    participant Lsof as lsof_or_port_listener_pids
    participant OS as OS_processes

    ProdRunner->>ProdRunner: PORT_PRESTART = read_env_value PORT (default 3000)
    ProdRunner->>PortCheck: is_port_listening(PORT_PRESTART)
    alt port_in_use
        ProdRunner->>ProdRunner: say Port in use — aggressively clearing
        ProdRunner->>Killer: _kill_port_squatters(PORT_PRESTART, PID)
        Killer->>Lsof: list listening PIDs on PORT_PRESTART
        Lsof-->>Killer: PID list
        loop for_each_pid
            Killer->>OS: kill -TERM pid
            OS-->>Killer: process may still exist
            Killer->>OS: sleep 1 then kill -KILL pid if still alive
        end
        ProdRunner->>ProdRunner: sleep 1
        ProdRunner->>PortCheck: is_port_listening(PORT_PRESTART)
        alt still_in_use
            ProdRunner->>ProdRunner: warn Port still occupied — forcing SIGKILL
            ProdRunner->>Lsof: lsof -t -iTCP:PORT_PRESTART -sTCP:LISTEN
            Lsof-->>ProdRunner: stray PID list
            ProdRunner->>OS: xargs kill -9 stray_pids
            ProdRunner->>ProdRunner: sleep 1
        end
    end

Loading

Sequence diagram for post-start health check and single auto-recovery

sequenceDiagram
    participant ProdRunner as prod_run_sh
    participant HealthUrl as resolve_health_url
    participant WaitHealth as wait_for_health
    participant PortCheck as is_port_listening
    participant Killer as _kill_port_squatters
    participant Systemd as systemctl
    participant NodeProc as node_index_js
    participant Telegram as telegram_api

    ProdRunner->>ProdRunner: say Running post-start health check
    ProdRunner->>HealthUrl: resolve_health_url()
    HealthUrl-->>ProdRunner: HEALTH_URL
    ProdRunner->>ProdRunner: derive HEALTH_PORT from HEALTH_URL
    ProdRunner->>ProdRunner: HEALTH_STATUS = unhealthy, PORT_STATUS = not-listening

    ProdRunner->>WaitHealth: wait_for_health(HEALTH_URL, 15, 2)
    alt health_success
        WaitHealth-->>ProdRunner: success
        ProdRunner->>ProdRunner: HEALTH_STATUS = healthy
    else health_fail
        WaitHealth-->>ProdRunner: failure
        ProdRunner->>PortCheck: is_port_listening(HEALTH_PORT)
        alt port_listening
            PortCheck-->>ProdRunner: true
            ProdRunner->>ProdRunner: warn Port still squatted — clear + one restart
            ProdRunner->>Killer: _kill_port_squatters(HEALTH_PORT, PID)
            Killer-->>ProdRunner: squatters cleared
            ProdRunner->>ProdRunner: sleep 1
            alt systemd_available
                ProdRunner->>Systemd: systemctl restart APP_NAME.service
                Systemd-->>ProdRunner: restart triggered
            else no_systemd
                ProdRunner->>NodeProc: kill PID (if set)
                ProdRunner->>NodeProc: nohup node index.js
            end
            ProdRunner->>ProdRunner: sleep 3
            ProdRunner->>ProdRunner: PID = get_bot_pid()
        end
        ProdRunner->>WaitHealth: wait_for_health(HEALTH_URL, 10, 2)
        alt final_health_success
            WaitHealth-->>ProdRunner: success
            ProdRunner->>ProdRunner: HEALTH_STATUS = healthy
        else final_health_fail
            WaitHealth-->>ProdRunner: failure
            ProdRunner->>ProdRunner: HEALTH_STATUS remains unhealthy
        end
    end

    ProdRunner->>PortCheck: is_port_listening(HEALTH_PORT)
    alt listening_now
        PortCheck-->>ProdRunner: true
        ProdRunner->>ProdRunner: PORT_STATUS = listening
    else still_not_listening
        PortCheck-->>ProdRunner: false
        ProdRunner->>ProdRunner: PORT_STATUS = not-listening
    end

    ProdRunner->>Systemd: systemctl is-active APP_NAME.service
    Systemd-->>ProdRunner: SYSTEMD_ACTIVE

    ProdRunner->>ProdRunner: _ADMIN_IDS = read_env_value ADMIN_IDS
    ProdRunner->>ProdRunner: _BOT_TOKEN = read_env_value TELEGRAM_BOT_TOKEN
    alt telegram_configured
        ProdRunner->>ProdRunner: build _REPORT from MAIN_LOG and ERROR_LOG
        loop for_each_admin
            ProdRunner->>Telegram: sendMessage(bot_token, admin_id, summary + _REPORT)
            Telegram-->>ProdRunner: 200 OK (ignored)
        end
    end

Loading

File-Level Changes

Change	Details	Files
Aggressively clear port conflicts before startup and simplify post-start health/auto-heal + Telegram reporting into a single, more robust pass.	Introduce _kill_port_squatters helper that prefers lsof to find listeners on a port and sends TERM then KILL, skipping the current process PID if provided. Replace free_port_if_conflicted pre-start logic with _kill_port_squatters and an extra lsof-based SIGKILL sweep if the port remains occupied. Rewrite the previous multi-phase "God-mode" heal section into a single post-start health check that waits for the health URL, performs one auto-recovery restart if the health port is still squatted, and then does a final health probe. Rework Telegram admin notifications to use read_env_value for ADMIN_IDS and TELEGRAM_BOT_TOKEN, send a concise deploy summary plus trimmed combined logs, and ensure notification reflects the final health/port/systemd state.	prod-run.sh
Tighten file permissions and improve robustness/observability of QA-related filesystem operations and admin/QA logging.	Ensure various log and artifact writes (bonus admin log, adminEventsLogFile, QA logs, QA provider state, SSH editor saves, atomic writes) use explicit encoding and restrictive file modes (generally 0o640 for logs and 0o600 for state/config/temp files). Refine QA_FS_SUPPRESS to be the single source of truth for suppressed errno codes, drop EEXIST from suppression, and harden error handling with optional chaining, safer message formatting, and optional stack inclusion in debug mode. Introduce tryWriteQaJson helper to apply QA_FS_SUPPRESS semantics per QA artifact write, then refactor ensureQaArtifacts to use it so individual failures do not block other QA files while remaining non-fatal overall. Improve QA directory and provider-state error logging to distinguish expected permission/readonly failures from unexpected conditions, while keeping the bot resilient when QA directories or files are unwritable.	index.js
(Potential) service unit adjustments associated with the new start/health behavior (no functional diff shown here).	runewager.service is touched, likely to align systemd behavior with the updated prod-run.sh health/port management, but the specific changes are not included in the provided diff.	runewager.service

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Rate limit exceeded

@gamblecodezcom has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b367aa67-19db-4657-b7ed-8df0b0c2f1fd

📥 Commits

Reviewing files that changed from the base of the PR and between 31f72b3 and 3c6c120.

📒 Files selected for processing (3)

• index.js
• prod-run.sh
• runewager.service

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/cpu-guard-script-DnD8u

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codeant-ai]

CodeAnt AI finished reviewing your PR.