Add a way to collect bug report data easily
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Right now when people filed bug reports, it's hard to know what is going on on the host side, how they are building the GPU code, if they are translating through naga, if vulkansdk is installed, what device they are targeting, the SPIR-V that is generated, etc.
We should have a simple way for users to dump all the data we need to debug which can be attached to a bug report or a gist. It can later be exposed in cargo-gpu
I'm not sure if rustc has something like this or we will have to create our own.
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 checking the cargo-gpu entry point and whether rustc already exposes comparable diagnostic or environment data. Define the dump contents for the host, GPU build, naga translation, Vulkan SDK, target device, and generated SPIR-V; done means users can produce one report suitable for attaching to a bug report or gist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, computer-graphics, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100