Disable debugger when running internal Ark code
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 337
- Forks
- 32
- Avg merge
- 8d 17h
- Merged PRs (30d)
- 11
Description
Setting a user breakpoint (e.g. via `debug()) on a base R function that is used internally by the Ark console can completely bork Ark.
To try and prevent this, we could auto-step with n whenever a debug prompt is invoked at unexpected times.
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.
Research direction
Start by tracing how Ark handles a debugger prompt while executing internal console code, then reproduce the failure by setting a breakpoint with debug() on a base R function used by Ark. Determine the existing prompt and stepping behavior; done means user breakpoints cannot disrupt Ark's internal execution and ordinary debugging still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, rust
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100