Support connecting to different clients without restarting the debuggee
还没有人认领这个 Issue。
评估
调研方向
Start by tracing the debugger server lifecycle when connecting to VSCode or Chrome, focusing on the methods extended onto the server. Determine how those extensions could be reverted or isolated when a client disconnects. Done means a debuggee can switch to another client without restarting and losing its current state; no files or tests are named.
由索引模型根据 Issue 内容生成。
描述
Your proposal
It would be great if after disconnecting from a debugger client (e.g. VSCode), we can connect to the debuggee with another client (e.g. Console). This can be useful because some debugger features like tracers is only available to console. But having to restart the debuggee for the console means losing its current state.
Currently it's not possible because once connecting to the VSCode/Chrome, the server would have extended with different methods. And there's no way to revert that.
- 主要语言
- Ruby
- 星标
- 1.3k
- 派生
- 146
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ruby/debug 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP 未关闭
难度 4/5 3-5 天 新手友好度 55/100
-
难度 3/5 1-2 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 52/100
-
难度 4/5 3-5 天 新手友好度 35/100
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
难度 2/5 1-3 小时 新手友好度 88/100
-
バグ
难度 1/5 1 小时以内 新手友好度 92/100
-
难度 2/5 1-3 小时 新手友好度 75/100
voxpupuli/puppet-epel#186 · 1 条评论 ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) 未关闭Bug Frontend
难度 2/5 1-3 小时 新手友好度 78/100