502 Bad Gateway with `v2`
See original GitHub issueUsing:
- name: 'Set up JDK'
uses: actions/setup-java@v2
with:
java-version: ${{ matrix.java }}
distribution: 'zulu'
Leads (sometimes) to:
https://github.com/sormuras/bach-application-template/runs/2321248297?check_suite_focus=true
Note: Jobs running on macOs and Windows in parallel did manage to setup Java as expected.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How To Fix a 502 Bad Gateway Error - Kinsta
The 502 bad gateway error specifically means that server received an invalid response from an inbound server. Check out these common causes ...
Read more >502 Bad Gateway - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 502 Bad Gateway server error response code indicates that the server, while acting as a gateway or ...
Read more >How to Fix 502 Bad Gateway Error - Hostinger
502 bad gateway is one of the many HTTP status codes. Follow this tutorial and learn what this 502 error means and how...
Read more >502 Bad Gateway Error [Solved] - freeCodeCamp
The causes of the 502 bad gateway error include an overloaded server, an error in the code, and yet-to-be-propagated domain names.
Read more >Bad Gateway Errors: Why They Happen and 5 Solutions - Okta
A 502 bad gateway message indicates that one server got an invalid response from another. In essence, you've connected with some kind of...
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 FreeTop 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
Top GitHub Comments
As Dmitry mentioned, we have added e2e tests scheduled twice per day (every test runs about ~150 test cases) and didn’t reproduce this issue for the last week. I will close this issue for now but we will keep these tests scheduled and will monitor them. Please let us know if you see this issue again. If it reproduces, we definitely should consider adding some kind of retry logic for action.
Thank you for providing information @sormuras. We added schedule for e2e in scope of this pull request to monitor this issue.