Skip to content

docs: Document Gateway Telegram Unicode-safe error handling (PR #1754)#453

Open
MervinPraison wants to merge 1 commit into
mainfrom
claude/issue-446-20260530-0619
Open

docs: Document Gateway Telegram Unicode-safe error handling (PR #1754)#453
MervinPraison wants to merge 1 commit into
mainfrom
claude/issue-446-20260530-0619

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

Fixes #446

Summary

Documents the Gateway Telegram Unicode-safe error handling feature from PraisonAI PR #1754, which fixed Windows charmap crashes when error messages contained Unicode characters.

Changes Made

  • Updated troubleshooting guide (docs/guides/troubleshoot-gateway.mdx) with new Windows charmap error section
  • Enhanced bot gateway docs (docs/features/bot-gateway.mdx) with Unicode-safe error handling notes and UTF-8 YAML support
  • Updated Telegram tool docs (docs/tools/external/telegram.mdx) with new user-facing error messages (quota, rate limit, auth, timeout)
  • Created comprehensive error handling page (docs/features/gateway-error-handling.mdx) following AGENTS.md standards with:
    • Hero Mermaid diagram using standard color scheme
    • Agent-centric Quick Start examples
    • Error pattern recognition table
    • Symbol replacement mappings
    • Best practices with AccordionGroup
    • Related pages with CardGroup
  • Updated navigation (docs.json) to include new page in Integration & Infrastructure section

Documentation Standards Compliance

✅ Follows AGENTS.md template structure
✅ Uses required Mintlify components (Steps, AccordionGroup, CardGroup)
✅ Includes hero Mermaid diagram with standard colors (#8B0000, #189AB4, #10B981, #F59E0B, #6366F1)
✅ Agent-centric code examples with correct imports
✅ Copy-paste runnable code blocks
✅ Concise writing style with one-sentence section intros
✅ Cross-links between related documentation pages

Test Plan

  • Documentation builds without errors
  • All cross-links resolve correctly
  • Mermaid diagrams render with proper colors
  • Code examples are syntactically correct
  • Navigation structure is valid JSON

🤖 Generated with Claude Code

- Add Windows charmap error troubleshooting section to gateway troubleshooting guide
- Add Unicode-safe error handling notes to bot gateway documentation
- Update Telegram tool documentation with new user-facing error messages
- Create comprehensive gateway error handling feature page following AGENTS.md standards
- Include Mermaid diagrams, proper component usage, and agent-centric examples
- Update docs.json to include new page in Integration & Infrastructure section

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 30, 2026 06:23
@qodo-code-review
Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 30, 2026

Warning

Review limit reached

@MervinPraison, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes and 31 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a23c80bc-a402-4601-991d-330a6a385a46

📥 Commits

Reviewing files that changed from the base of the PR and between ad3daba and 689fd69.

📒 Files selected for processing (5)
  • docs.json
  • docs/features/bot-gateway.mdx
  • docs/features/gateway-error-handling.mdx
  • docs/guides/troubleshoot-gateway.mdx
  • docs/tools/external/telegram.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/issue-446-20260530-0619

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 and usage tips.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds comprehensive documentation for Gateway Error Handling, introducing Unicode-safe error handling for Gateway bot replies to prevent encoding crashes (such as 'charmap' codec errors on Windows). It includes a new feature guide, troubleshooting steps, and updates to the Telegram tool documentation. Feedback on the documentation includes enclosing Mermaid flowchart node labels with emojis/spaces in double quotes to prevent parsing errors, and correcting the smart quotes table row to use actual curly smart quotes instead of straight double quotes.

Comment on lines +13 to +16
Exception[⚠️ Exception] --> Extract[🔍 Extract Root Cause]
Extract --> Sanitize[🔧 Sanitize to ASCII]
Sanitize --> Reply[💬 User Reply]
Exception --> Log[📝 Full Unicode Log]
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

In Mermaid flowcharts, node labels containing special characters (such as emojis like ⚠️, 🔍, 🔧, 💬, 📝) and spaces should be enclosed in double quotes (e.g., Node["text"]) to prevent rendering or parsing errors across different Markdown parsers.

        Exception["⚠️ Exception"] --> Extract["🔍 Extract Root Cause"]
        Extract --> Sanitize["🔧 Sanitize to ASCII"]
        Sanitize --> Reply["💬 User Reply"]
        Exception --> Log["📝 Full Unicode Log"]

| `✗` | `X` | Cross mark |
| `→` | `->` | Right arrow |
| `…` | `...` | Ellipsis |
| `"` `"` | `"` | Smart quotes |
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The table row for smart quotes uses straight double quotes (") in the Unicode column instead of actual curly smart quotes ( and ). This defeats the purpose of demonstrating the replacement of smart quotes with straight quotes.

| `“` `”` | `"` | Smart quotes |

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

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.

[Docs] Document Gateway Telegram Unicode-safe error handling (PR #1754) — Windows charmap crash fix

2 participants