provide help & links for some build errors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
coming from things like this issue.
There are certain errors where we as maintainers (or more experienced crate maintainers) directly see what's the issue.
What we could do is to search for certain patterns (just with a regex), and provide an explanation of the likely problem.
Examples (there's probably more):
kind: ReadOnlyFilesystem-> link to https://docs.rs/about/builds#read-only-directories- sigkill -> memory issues
- timeouts?
If we include our thoughts in #878, we could also make this even better by storing the specific rustwide error (if it's enough?) and using that.
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
Review the build-error handling discussed in this issue and the related design in #878; no specific file or test is named. Identify how errors are represented and where guidance could be attached, then verify that supported patterns provide the relevant read-only-directory, memory, or timeout explanations and links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100