-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intermittent 404 Not Found on /pulls github calls #1905
Comments
I think this might be related with the failure on e2e tests that happened the other day after merging #1884 |
it feels like part of the issue might be the lack of exponential backoff in the retry fix https://github.com/runatlantis/atlantis/pull/1131/files current code it does look like its doing geometirc backoff now, but its unclear if we need to switch to exponential to resolve. |
Maybe it's worth also adding extra logging to the section to record the fact that retries are happening? |
Confirmed that we are experiencing this issue as well in 0.17.5. Would love for this to get fixed ASAP. |
This issue is happening in 0.17.4 as well. |
Looks like something similar to #1131 is needed but in atlantis/server/events/vcs/github_client.go Lines 123 to 126 in 1b30fe0
|
Similar to runatlantis#1131, we see this for /files/ too, resulting in a plan error. Closes runatlantis#1905
Similar to runatlantis#1131, we see this for /files/ too, resulting in a plan error. Closes runatlantis#1905
is this still an issue with |
It's happening with me on v0.20.1 |
Similar to runatlantis#1131, we see this for /files/ too, resulting in a plan error. Closes runatlantis#1905
its happening on 0.22 as well |
Community Note
Overview of the Issue
I'm experiencing intermittent 404s on PRs. Atlantis leaves the following comment in the PR:
Reproduction Steps
This happens intermittently but the steps are to:
Logs
Logs
Environment details
Atlantis
v0.17.5
Atlantis server-side config file:
Repo
atlantis.yaml
file (atlantis is actually disabled for theEnvironment variables:
Additional Context
Similar to
The text was updated successfully, but these errors were encountered: