R2NorthstarTools / R2NorthstarTools/FlightCore
Remote log mod-install sanity check failure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Remote logging sanity-check failure of a mod via Sentry should give us a quick way to see what mods are failing to install.
We can then manually inspect them to see whether they are actually malformed or whether there was another issue during installation, possibly within FlightCore/libthermite.
Bringing this up as according to @ASpoonPlaysGames on Discord there have been more sanity check failures of mod installations recently.
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.
Research direction
Start by tracing the remote logging sanity-check path for mod installations and how failures are reported to Sentry. Done means a failed installation identifies the mod clearly enough for maintainers to inspect whether it is malformed or affected by FlightCore/libthermite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100