secondlife / secondlife/viewer
Migrate to new BugSplat database and standardize application naming
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Description
Update crash reporting to use the secondlife BugSplat database and standardize all viewer variants under a single viewer application name.
Description
The Second Life viewer currently uploads crashes to the SecondLife_Viewer_2018 database. As you may have noticed, we are not in the year 2018. Additionally, different viewer versions are registering as separate applications (e.g., "Second Life Develop", "Second Life Release", "Second Life Release edu"), fragmenting our crash data.
Acceptance Criteria
- All crash reports upload to
secondlifedatabase (notSecondLife_Viewer_2018) - All viewer variants register as application name
viewerin BugSplat
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100 (replace 100 with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/try to let everyone know!🙌 And when they open the PR, they can comment
/claim #4534 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @bennettgoble (replace 20 with the amount, and @bennettgoble with the user to tip).📖 If you want to learn more, check out our documentation.
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
Search the repository for SecondLife_Viewer_2018 and the existing BugSplat application-name handling to locate the crash-reporting entry points. Verify that the configuration uses the secondlife database and that every viewer variant reports as viewer, then confirm both acceptance criteria through the relevant crash-upload path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100