Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
FOSSA workflow in Pull Requests is flaky
See original GitHub issueLooking at the history of FOSSA workflow runs, they sometimes fail due to server error.
INFO Uploading analysis...
FATAL Error during upload: Error response from API: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
Possible Solution
- Few delayed retries when upload fails due to errors.
Previous discussion https://github.com/backstage/backstage/pull/4077#issuecomment-764463876
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Stacked Diffs Versus Pull Requests | Jackson Gabbard's Blog
The typical workflow is to work right on top of master, committing to master as you go. For each of the commits, you...
Read more >DEVELOPMENT.md - m3db/m3 - Sourcegraph
Commit fixes or skips for flaky tests or other failures first. Your pull request is most likely to be accepted if it: Includes...
Read more >horovod - Projects | FOSSA
If you feel the results are incorrect, take a peek at the language documentation for known issues or reach out to team Fossa...
Read more >How To Build Only Master Branch Using Circleci - ADocLib
These rules can be that commits can be only added through pull requests a successful build I made some changes and committed them...
Read more >MergeQueue | Automate your Github workflows
Github merge workflow, keep your builds green. ... Combine two or more Pull Requests together to reduce your CI and merge more ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I Googled the issue for some inspiration and landed back here as the second top result. Oh well.
Our idea for a fix is to wrap the fossa execution in a script that does 1 or 2 retries, and then ignores the error if it’s a 502 by inspecting the output of the fossa command