refactor(rtps): adopt the new Socket option API (set_receive_buffer_size)

[finger563]

Small fast-follow to #714 (the socket set_option / buffer-size API).

A repo-wide sweep for manual setsockopt/getsockopt on native handles found one call site outside the socket component: the RTPS transport's SO_RCVBUF enlarge (used, under RTPS_ENABLE_FRAGMENTATION, to keep a burst of DATA_FRAG datagrams from being dropped before the reactor drains them). This migrates it to the new API:

// before
int rcvbuf = 4 * 1024 * 1024;
::setsockopt(channel.socket->native_handle(), SOL_SOCKET, SO_RCVBUF,
             reinterpret_cast<const char *>(&rcvbuf), sizeof(rcvbuf));
// after
(void)channel.socket->set_receive_buffer_size(4 * 1024 * 1024);

Behaviour is unchanged (still best-effort — failure ignored). No other repo sites needed migrating (the only other SO_* mention is a docstring in the python bindings).

Verified: host lib builds (fragmentation on, so the migrated path is compiled) and rtps_facade_frag passes.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Refactors RTPS transport socket receive-buffer sizing to use the newer socket option API (set_receive_buffer_size) instead of calling setsockopt on the native handle.

Changes:

• Replace direct setsockopt(..., SO_RCVBUF, ...) usage with socket->set_receive_buffer_size(...) in the RTPS transport channel setup.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

✅Static analysis result - no issues found! ✅

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.