Sporadic 403 errors when fetching Characterization results
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
(Using WebAPI 2.14.0 / Atlas 2.14.1)
Generated Characterization results can be returned when clicking on them.
Actual behavior
Sporadically, we see these 403 errors when trying to view the results of a Characterization:
This then becomes a problem for all users. The only workaround seems to be to simply create a new one, generate it, then view it. Somehow then this issue clears for all users.
Steps to reproduce behavior
- Create and generate a characterization
- Try to view the results, perhaps after a few days?
Tagging @konstjar
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
No source file or test is named. Start by reproducing the characterization flow from the reported steps and inspect the request that fetches generated results, including the conditions surrounding the sporadic 403 response. Done means identifying and fixing the cause so existing characterization results remain viewable for all users, then adding or updating coverage for the failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100