Fix Error: calling "initialize": invalid trailing data at the end of stream.

[gajzzs]

#430

Summary by CodeRabbit

• Bug Fixes
  • Improved output handling on Windows systems to prevent unwanted formatting characters from appearing in console output.

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

[coderabbitai]

Walkthrough

The changes modify stdout handling on Windows by setting stdin and stdout to binary mode, then wrapping stdout with a custom CRStripper proxy that removes carriage return characters from both bytes and string writes, enforcing LF newlines with line buffering enabled.

Changes

Cohort / File(s)	Summary
Windows stdout carriage return handling Server/src/main.py	Configures Windows stdin/stdout to binary mode and wraps stdout with a custom CRStripper proxy to strip \r characters from output, enforce LF newlines, and enable line buffering

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Custom proxy implementation: The CRStripper wrapper requires careful review to ensure it correctly handles both bytes and string writes without introducing encoding issues or breaking output behavior
• Binary mode interaction: Verify that setting binary mode and wrapping with TextIOWrapper doesn't conflict with the application's existing stdout handling elsewhere in the codebase
• Platform-specific logic: Windows-only code path should be tested across different console and pipe scenarios to confirm CR stripping works as intended

Poem

🐰 On Windows where carriage returns roam,
A stripper arrives to sweep them back home,
LF newlines stand strong, so neat and so clean,
Binary mode whispers, "I'll fix what's unseen,"
Line buffering hops with a leap and a bound! 🍃

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title describes fixing an error related to 'invalid trailing data at the end of stream', but the actual changes involve Windows-specific stdout/stdin binary mode handling and carriage return stripping, which are not directly mentioned in the title.	Update the title to accurately reflect the main change, such as 'Fix Windows stdout carriage return handling' or 'Strip carriage returns from stdout on Windows', to better represent the actual code modifications.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e0ef23 and aa81ee6.

📒 Files selected for processing (1)

• Server/src/main.py (1 hunks)

[gajzzs]

@dsarno is there any issue in this PR ?