Missing tips for the docs

[mihow]

Summary

• Instructions on properly stopping the new ui-dev container
• Tips on troubleshooting RabbitMQ after resolving some issues on live

Summary by CodeRabbit

• Documentation
  • Added instructions for stopping the ui-dev Docker Compose profile with explicit commands.
  • Added troubleshooting guidance for worker monitoring issues, including diagnosis and resolution steps for common problems.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for antenna-preview ready!

Name	Link
🔨 Latest commit	b02eef1
🔍 Latest deploy log	https://app.netlify.com/projects/antenna-preview/deploys/692665b4a5bbe50008878ead
😎 Deploy Preview	https://deploy-preview-1066--antenna-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 73 (🟢 up 35 from production) Accessibility: 89 (🟢 up 9 from production) Best Practices: 92 (🔴 down 8 from production) SEO: 100 (🟢 up 8 from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

Documentation updates adding operational guidance to the project. README.md introduces commands for stopping the ui-dev Docker Compose profile, while docs/WORKER_MONITORING.md adds two new troubleshooting sections addressing worker task execution failures and stale worker queue issues.

Changes

Cohort / File(s)	Change Summary
Docker Compose profile management README.md	Added explicit commands for stopping and bringing down the ui-dev Docker Compose profile, including alternate wildcard profile syntax
Worker troubleshooting guides docs/WORKER_MONITORING.md	Added two troubleshooting sections: one addressing workers appearing connected but tasks not executing (linked to RabbitMQ disk space alarm), and another covering stale worker queue issues from celery inspect

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Documentation-only changes with no code logic or structural modifications
• Straightforward additions of operational guidance and troubleshooting procedures
• Consistency check needed for documentation formatting and clarity

Possibly related PRs

• Add Celery worker memory and task limits for leak prevention #1051: Introduces the monitoring documentation guide that these troubleshooting sections extend with additional diagnostic procedures.

Suggested reviewers

• carlosgjs

Poem

🐰 With Docker commands, the profile falls quiet,
And workers now have answers to try it,
RabbitMQ alarms, and queues gone stale,
Our docs now shine—let troubleshooting prevail! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description covers the summary but is largely incomplete, missing critical sections like List of Changes, Related Issues, Detailed Description, How to Test, and the required checklist.	Expand the description to include: explicit list of changes (files modified), related issue references, detailed explanation of documentation additions, testing instructions, and completion of the required checklist items.
Title check	❓ Inconclusive	The title 'Missing tips for the docs' is vague and generic, using non-descriptive language that doesn't convey the specific nature of the documentation changes.	Use a more specific title such as 'Add ui-dev Docker Compose shutdown and RabbitMQ troubleshooting documentation' to clearly indicate what documentation content is being added.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/ui-dev-container

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 00d71ca and b02eef1.

📒 Files selected for processing (2)

• README.md (1 hunks)
• docs/WORKER_MONITORING.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Agent
• GitHub Check: test
• GitHub Check: Redirect rules
• GitHub Check: Header rules
• GitHub Check: Pages changed

🔇 Additional comments (3)

README.md (1)

50-53: Clear and helpful guidance for stopping ui-dev container.

The addition documents an important operational detail that wasn't previously explicit. Both command options are correct and well-positioned in context.

docs/WORKER_MONITORING.md (2)

158-158: Service URL inconsistency: verify RabbitMQ Management UI hostname.

Line 136 documents RabbitMQ Management UI access as http://localhost:15672, but line 158 in the newly added troubleshooting section references http://rabbitmq-server:15672. In the local Docker Compose development environment, both should be consistent.

Verify whether rabbitmq-server is the correct container service name in the compose setup or if localhost should be used instead to match the documented access pattern.

Also applies to: 136-136

---

191-208: Solid addition to troubleshooting guidance with clear cause and resolution.

This section effectively documents a specific operational issue (stale pidbox queues) with both UI-based and CLI alternatives. The explanation of why this happens (worker restarts leaving orphaned queues) is helpful context.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

[Copilot]

Pull request overview

This PR adds helpful documentation for troubleshooting RabbitMQ issues and instructions for properly stopping the ui-dev container with Docker Compose profiles.

• Added two new troubleshooting sections to WORKER_MONITORING.md covering RabbitMQ disk space alarms and stale worker queues
• Added instructions to README.md for stopping the ui-dev container using the correct profile syntax

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
README.md	Added documentation on how to properly stop the ui-dev container by specifying the profile when running docker compose down or stop
docs/WORKER_MONITORING.md	Added two comprehensive troubleshooting sections: one for diagnosing and resolving RabbitMQ disk space alarms that block connections, and another for handling stale worker pidbox queues that break celery inspect commands

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Inconsistent RabbitMQ Management UI URL. Line 136 uses http://localhost:15672 while line 158 uses http://rabbitmq-server:15672.

For consistency and clarity, both should use the same URL. If the UI is accessed from the host machine (outside Docker), localhost is correct. If accessed from within Docker containers, rabbitmq-server would be correct.

Based on the context at line 136 which shows "Access at: http://localhost:15672", the URL at line 158 should likely be:

http://localhost:15672

Suggested change

	1. Check RabbitMQ Management UI (http://rabbitmq-server:15672) → Connections tab
	1. Check RabbitMQ Management UI (http://localhost:15672) → Connections tab