Skip to content

docs: add troubleshooting section to README#650

Open
ankitasahu83964 wants to merge 1 commit into
sreerevanth:mainfrom
ankitasahu83964:docs/troubleshooting-clean-v2
Open

docs: add troubleshooting section to README#650
ankitasahu83964 wants to merge 1 commit into
sreerevanth:mainfrom
ankitasahu83964:docs/troubleshooting-clean-v2

Conversation

@ankitasahu83964

@ankitasahu83964 ankitasahu83964 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Description

This PR adds a Troubleshooting section to the README to help contributors resolve common setup issues.

Changes

  • Added fix for ModuleNotFoundError
  • Added Docker troubleshooting steps
  • Added guidance for port conflicts (8000 and 3000)
  • Added Python version check
  • Added environment variable setup for Linux/macOS and Windows

Type of Change

  • Documentation

Checklist

  • Documentation updated
  • No code changes

Summary by CodeRabbit

  • Documentation
    • Added a troubleshooting section covering dependency installation, Docker availability, port conflicts, supported Python versions, and missing environment variables.
    • Included platform-specific setup commands and clarified the requirement for Python 3.12 or later.

@vercel

vercel Bot commented Jul 23, 2026

Copy link
Copy Markdown

@ankitasahu83964 is attempting to deploy a commit to the sreerevanth's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

README.md adds a troubleshooting section covering dependency installation, Docker startup, port conflicts, Python 3.12+ requirements, and missing environment variables.

Changes

README troubleshooting guidance

Layer / File(s) Summary
Document common setup fixes
README.md
Adds setup troubleshooting instructions for development dependencies, Docker verification, ports 8000/3000, Python version checks, and .env creation on Linux/macOS and Windows PowerShell.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related issues

Possibly related PRs

Suggested labels: Easy

Suggested reviewers: sreerevanth, sakethsumanbathini, rishabhextra365-lang

Poem

A bunny found a README thorn,
And tucked in fixes bright as morn.
Docker hops, ports clear the way,
Python checks now know what to say.
.env blooms where secrets stay—
Setup bounces on its way!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: adding a troubleshooting section to the README.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 292-308: Expand the “Port already in use” section with
platform-specific commands to terminate the identified process, and document how
to remap the host ports. Reference the corresponding Docker Compose
API/dashboard port mappings and frontend development-server port configuration
so users can choose alternate ports.
- Around line 340-341: Remove the stray trailing “q” from the final sentence in
the README so it ends with “application.”
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d18b13f7-37c8-4764-af63-3ae515a6a53c

📥 Commits

Reviewing files that changed from the base of the PR and between 0a2e15f and bda9c42.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +292 to +308
### Port already in use

If port **8000** (API) or **3000** (Dashboard) is already in use, stop the process using that port or choose a different port.

**Linux/macOS**

```bash
lsof -i :8000
lsof -i :3000
```

**Windows (PowerShell)**

```powershell
netstat -ano | findstr :8000
netstat -ano | findstr :3000
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Include commands to resolve the port conflict.

These commands only identify the process holding the port; they do not show users how to stop it or how to remap the host port. Add platform-specific follow-up commands and point to the corresponding Compose/frontend port configuration.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 292 - 308, Expand the “Port already in use” section
with platform-specific commands to terminate the identified process, and
document how to remap the host ports. Reference the corresponding Docker Compose
API/dashboard port mappings and frontend development-server port configuration
so users can choose alternate ports.

Comment thread README.md
Comment on lines +340 to +341
Then update the required values before starting the application.q

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Remove the trailing q from the final sentence.

-Then update the required values before starting the application.q
+Then update the required values before starting the application.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Then update the required values before starting the application.q
Then update the required values before starting the application.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 340 - 341, Remove the stray trailing “q” from the
final sentence in the README so it ends with “application.”

@github-actions

Copy link
Copy Markdown
Contributor

🧪 PR Test Results

Check Result
Tests (pytest tests/) ✅ success
Lint (ruff check .) ✅ success
Coverage (agentwatch) 74.01%

Python 3.12 · commit bda9c42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant