Fix JSON-RPC output by redirecting console logs to stderr

[parmar-abhinav]

Summary

This PR fixes an issue where console.log statements were writing to stdout, which interfered with the JSON-RPC protocol output. Since JSON-RPC messages are transmitted over stdout, any additional log text caused parsing errors on the client side.

Changes

Replaced console.log with console.error for non-protocol logging and debugging messages.

Summary by CodeRabbit

• Chores
  • Updated database connection logging output handling
  • Applied code formatting standards

[coderabbitai]

Walkthrough

A logging destination is redirected in the FalkorDB service file, moving connection success messages from stdout to stderr. A trailing newline is added for proper file formatting. No public entity signatures are modified.

Changes

Cohort / File(s)	Change Summary
Logging and formatting updates src/services/falkordb.service.ts	Modified success logging to emit to stderr instead of stdout; added trailing newline to end of file

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file with minimal, localized changes
• Simple logging redirection (console.log → console.error)
• No logic modifications or behavioral impact beyond output stream

Poem

🐰 The rabbits cheered as logs now flow,
Through stderr's path instead of stdout's glow,
With newlines tidy, files sit neat,
A tiny fix, but oh so sweet! ✨

Pre-merge checks and finishing touches

✅ 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 directly matches the main change: redirecting console logs from stdout to stderr to fix JSON-RPC protocol output.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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: 0

🧹 Nitpick comments (1)

src/services/falkordb.service.ts (1)

25-25: Consider adding a comment explaining the stderr usage.

While this change correctly solves the JSON-RPC stdout pollution issue, using console.error for success messages is semantically confusing. Log monitoring and aggregation tools typically treat stderr as errors, which may cause false alerts or misclassification.

Consider adding a brief comment explaining the JSON-RPC constraint, or introducing a logging abstraction that makes the intent clearer.

Example with comment:

-      console.error('Successfully connected to FalkorDB');
+      // Log to stderr to avoid polluting stdout (used for JSON-RPC protocol messages)
+      console.error('Successfully connected to FalkorDB');

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d94282 and a66a5ca.

📒 Files selected for processing (1)

• src/services/falkordb.service.ts (2 hunks)

🔇 Additional comments (1)

src/services/falkordb.service.ts (1)

76-76: LGTM!

Adding the trailing newline is good practice and aligns with standard formatting conventions.

[parmar-abhinav]

Hi @gkorland, could you please review this PR.

[parmar-abhinav]

Hi @gkorland could you please check this PR.

[Copilot]

Pull request overview

Fixes JSON-RPC protocol corruption by ensuring non-protocol logs don’t write to stdout (reserved for JSON-RPC messages).

Changes:

• Redirected a successful DB connection log from console.log (stdout) to console.error (stderr)

---

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

[Copilot]

Using console.error for a success/informational message can cause it to be treated as an error by log collectors/CI and may trigger alerts. Consider routing to a logger with configurable streams/levels (e.g., logger.info(...) mapped to stderr for JSON-RPC safety), or use console.warn/an info-level logger explicitly configured to write to stderr.

Suggested change

	console.error('Successfully connected to FalkorDB');
	console.log('Successfully connected to FalkorDB');