OSS Fuzz issues contain broken link, discouraging contributions
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
It seems that https://github.com/google/oss-fuzz/pull/13394 wasn't enough, since I still can't access the OSS Fuzz reports.
Example:
#8953
Gives me:
I don't really know how to fix this :(
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 comparing issue #8953 with the prior OSS-Fuzz pull request #13394 and inspect the broken report link shown in this issue. Identify where the link is generated or maintained, then verify that an OSS-Fuzz report is reachable after the change.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100