Create and send crash dumps
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue names no files, tests, or entry points. Start by locating the engine's crash-reporting path and device UID access, then determine how crash dumps are sent and what data must be hashed before transmission; done means a crash dump can be sent with a safely hashed device identifier.
Written by the indexing model from the issue text.
Description
Generate device hash from the GPU/CPU/MB UIDs. Use crypto hash for safety.
- Dominant language
- C++
- Stars
- 35
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 cfnptr/garden
-
bug question
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
improvement research
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
improvement VulkanAPI
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
feature render
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·