usability suggestions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
After having run a couple thousand rr records now, I have some new-user suggestions.
-
It would be nice to auto-pack the traces after they are generated, even if this takes an additional flag to do so.
-
the latest-trace symlink makes it a problem to do parallel runs.
I have a 48 cpu box, but I have to run rr record -h chaos runs one-at-a-time and sequentially, because otherwise they step on each others toes via that symlink, and the two parallel scripts get confused when trying to pack the latest after a run.
And I want to say: wow! rr is fantastic. I wish I discovered it earlier! rr is such an incredible force multiplier. It's already found a ton of bugs in the tsan/race detector part of the Go runtime. cf https://github.com/golang/go/issues/74019 and https://github.com/glycerine/rr_binary_for_issue74019?tab=readme-ov-file#analysis
rr record -h (chaos mode) makes Go's race detector find issues even in code I thought was race free. Fantastic!
Thank you!
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 the rr record -h chaos workflow, trace packing, and the latest-trace symlink behavior described in the issue. Determine how an optional auto-pack mode and parallel recording should behave; done means parallel runs no longer interfere and generated traces can be packed automatically when requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100