Line breakpoints aren't shared between processes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Reproduce the behavior with the Rails/Puma multi-process setup described in the issue, using five workers and line breakpoints. Then inspect the debugger's process handling mechanism; done means a line breakpoint added to one process stops requests handled by every process, with behavior checked in VSCode attach mode.
Written by the indexing model from the issue text.
Description
Your environment
ruby -v:3.1.0rdbg -v:1.6.0
Describe the bug
When the debuggee application has multiple processes, line breakpoints added to 1 of them won't be shared to other processes.
This will cause inconsistent breakpoint stop because only that process will stop and others won't.
To Reproduce
This issue should happen to any application that:
- Has multiple processes
- Uses line breakpoints
But reproducing it with VSCode is easier:
-
Create a new rails application
-
In
config/puma.rb, setthreads 1, 1 # limit the threads number to 1 will increase the reproduction chance # other configs workers 5 # increase this number will also help reproduction -
Start the server with
bundle exec rdbg -c -- bundle exec rails s -
Set a breakpoint
-
Attach the debugger
-
Sending requests to the Rails app
-
The breakpoint should stop at some requests but not all of them
Expected behavior
The breakpoints should stop at every request
Additional context
@ko1 mentioned that:
- Resolving this will require rewriting a big part of the process handling mechanism
- Possible workarounds: 1) Use only 1 process or 2) For VSCode users, use launch mode instead
- There are no timeline for this issue yet (probably not before Ruby 3.2 is out)
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ruby/debug
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100