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

Multithread in ruby-dbus

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

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading the update_buffer function and its IO.select usage, which the issue identifies as the source of the multithreading problem. Trace how requests and responses are associated with threads, then determine whether the proposed dispatch design is viable; done would require an agreed implementation direction, not just a patch.

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

描述

Hi,

We quite need for our project to use ruby-dbus multhreaded. This feature is not supported as reported in 20 - 21 -22. We are thinking about an implementation and we want to have an enlightened opinion before coding it.

The problem seems to be due to update_buffer function and IO.select. Update_buffer function doesn’t know from which does come the previous request and the first thread that take IO.select income takes the request. A way to solve it may be to dedicate a thread that wait IO.select and return the buffer to the according thread:

if message-type is METHOD_CALL or SIGNAL, return to main thread.
if MESSAGE_RETURN, return to concerned thread. To do so, we need when sending a message to log in a hash (for example) the thread it cames from.

The thread will wait a Thread.stop and will be restarted from the dedicated one with a Thread.run

Do you agree with this implementation, do you see limitations from that ?

主要语言
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 摘要。