fix manager crashloop

[Despire]

Summary by CodeRabbit

• Chores
  • Configured a new infrastructure refresh interval for the manager component to ensure timely system updates.

[coderabbitai]

Walkthrough

Adds the MANAGER_TICK_FOR_INFRA_REFRESH=100 environment variable to the claudie configuration file, establishing a ticking interval for infrastructure refresh operations on the manager component.

Changes

Cohort / File(s)	Summary
Configuration manifests/claudie/.env	Adds environment variable MANAGER_TICK_FOR_INFRA_REFRESH=100 to configure the manager component's infrastructure refresh ticking interval.

Possibly related PRs

• Load tick for infra refresh from CM in manager Deployment #1983: Wires the MANAGER_TICK_FOR_INFRA_REFRESH environment variable value into the manager Deployment from a ConfigMap, complementing this configuration addition.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix manager crashloop' is related to the changeset which adds a manager tick interval configuration to prevent infrastructure refresh thrashing, but it does not clearly convey what the actual fix entails or mention the specific configuration change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/crashloop

---

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.}

[coderabbitai]

🧹 Nitpick comments (1)

manifests/claudie/.env (1)

19-19: LGTM — straightforward fix for the missing env var.

The value 100 is reasonable for a refresh tick interval. One optional nit: a brief inline comment noting the approximate wall-clock duration (e.g., # ~16.7 min at 10 s/tick) would help operators tuning this value without needing to cross-reference the service code.

Based on learnings, MANAGER_TICK_FOR_INFRA_REFRESH intentionally accepts 0 for constant refresh, so the chosen non-zero default of 100 aligns with the intended semantics.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@manifests/claudie/.env` at line 19, Add an inline comment next to the
MANAGER_TICK_FOR_INFRA_REFRESH env var documenting the approximate wall-clock
duration for the chosen default (e.g., “# ~16.7 min at 10 s/tick”) and mention
the accepted special value 0 for constant refresh; update the
MANAGER_TICK_FOR_INFRA_REFRESH line to include that brief explanatory comment so
operators can tune the value without checking service code.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@manifests/claudie/.env`:
- Line 19: Add an inline comment next to the MANAGER_TICK_FOR_INFRA_REFRESH env
var documenting the approximate wall-clock duration for the chosen default
(e.g., “# ~16.7 min at 10 s/tick”) and mention the accepted special value 0 for
constant refresh; update the MANAGER_TICK_FOR_INFRA_REFRESH line to include that
brief explanatory comment so operators can tune the value without checking
service code.