RCBC-550: Access C++ log level using C++ core API instead of spdlog's default logger

[DemetrisChr]

Motivation

Backend.get_log_level results in a segmentation fault when used after a process fork. The reason for that is that we get the log level from spdlog's default logger, which is destroyed by the C++ SDK after the fork event (the SDK doesn't actually use spdlog's default logger). We should use the logger API provided by the C++ SDK instead of using the spdlog API directly. This affected Cluster#connect when using the default ThresholdLoggerTracer as it calls Backend.get_log_level

Change

• Use the C++ SDK's logger API to access and set the log level, instead of directly using the spdlog API.

[Copilot]

Pull request overview

Updates the Ruby client’s native logger integration to query/set log levels via the Couchbase C++ core logger API (instead of spdlog’s default logger), and adds a regression test for RCBC-550 covering connect-after-fork behavior.

Changes:

• Switch Backend.set_log_level / Backend.get_log_level to use core::logger::{set_log_levels,get_lowest_log_level}.
• Add a regression test that forks a process and connects/disconnects in the child.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
test/couchbase_test.rb	Adds a fork-based regression test for RCBC-550.
ext/rcb_logger.cxx	Uses C++ core logger API for log-level set/get instead of spdlog global logger.

---

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

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.