Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Better support for monitoring DBus messages & example

未关闭
#92 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
ruby

调研方向

Start with DBus::Connection, its #process behavior, and the registered @signal_matchrules, then compare them with the linked functional example and dbus-monitor behavior. Define how BecomeMonitor should be exposed and how processing should handle the server write-close; done means monitoring works without monkey patching and matches the requested behavior.

由索引模型根据 Issue 内容生成。

描述

It would be nice to have better support for monitoring/eavesdropping on messages sent across the bus. I have made a functional example but it requires a bit of monkey patching to change the library's behavior. This is the same functionality provided by the dbus-monitor(1) command.

  1. Support for another flag in match rules, though I'm not 100% certain it's needed for new enough implementations. I'm doing this to behave the same way dbus-monitor does.
  2. After calling BecomeMonitor, the socket becomes write-closed by the server. So the default behavior of #process no longer applies.

I think this is a useful feature, so I'd like to see this upstreamed. Not certain on the exact design though. A special #become_monitor method on DBus::Connection that re-uses the registered @signal_matchrules?

主要语言
Ruby
星标
174
派生
51
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

mvidner/ruby-dbus 的其他 Issue

查看 mvidner/ruby-dbus 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。