-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[BitBucket] Failed calls to fetch .gitpod.yml
are silently ignored
#11649
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
Labels
Comments
I would expect that the prebuild process should cancel with a warning message if it cannot access the file Could we also please
|
Yes, it should show as errored. |
svenefftinge
added a commit
that referenced
this issue
Jul 26, 2022
fixes [BitBucket] Failed calls to fetch `.gitpod.yml` are silently ignored #11649
1 task
svenefftinge
added a commit
that referenced
this issue
Jul 26, 2022
fixes [BitBucket] Failed calls to fetch `.gitpod.yml` are silently ignored #11649
roboquat
pushed a commit
that referenced
this issue
Jul 27, 2022
fixes [BitBucket] Failed calls to fetch `.gitpod.yml` are silently ignored #11649
Repository owner
moved this from In Progress
to Done
in 🍎 WebApp Team
Jul 27, 2022
flaming-codes
pushed a commit
to flaming-codes/gitpod
that referenced
this issue
Aug 1, 2022
fixes [BitBucket] Failed calls to fetch `.gitpod.yml` are silently ignored gitpod-io#11649
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
https://github.com/gitpod-io/gitpod/blob/main/components/server/src/bitbucket/bitbucket-file-provider.ts#L65
silently ignores (debug) thrown errors and as a result the caller is interpreting it as no config and continues with the project config and eventually inferring one. This results in strange and surprising behavior. We should bail out if this happens.
I found this in the logs:
Steps to reproduce
try often enough
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: