Emit a helpful logging message on reused object server

[pevogam]

Summary by CodeRabbit

• Chores
  • Enhanced logging to provide clearer visibility when an existing remote object server connection is reused, improving diagnostics and monitoring without changing behavior.

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

[coderabbitai]

Walkthrough

An info log message was added in get_remote_object (aexpect/remote_door.py) immediately after binding a remote object to indicate that an existing remote object server is being reused. There are no control-flow or behavioral changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly and accurately describes the main change: adding a logging message when a remote object server is reused.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5b92f33 and af49596.

📒 Files selected for processing (1)

• aexpect/remote_door.py

🔇 Additional comments (1)

aexpect/remote_door.py (1)

629-629: LGTM! Helpful observability improvement.

The log message clearly indicates that an existing remote object server is being reused, improving debugging and operational visibility. The INFO level is appropriate and consistent with other operational messages in this file.

---

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)

aexpect/remote_door.py (1)

625-629: Consider using LOG.info() instead of LOG.warning() for routine server reuse.

The log message describes a normal operational scenario—successfully binding to an existing server—rather than a warning condition. Using LOG.warning() here may clutter warning logs with informational messages that don't indicate problems.

🔎 Proposed change to use INFO level

         remote_object = Pyro4.Proxy(f"PYRONAME:{object_name}@{host}:{port}")
         # noinspection PyProtectedMember
         remote_object._pyroBind()
-        LOG.warning("Previous remote object server running, reusing it as is")
+        LOG.info("Previous remote object server running, reusing it as is")

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02e782c and 5b92f33.

📒 Files selected for processing (1)

• aexpect/remote_door.py

[ldoktor]

Wouldn't debug loglevel suffice here?