-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
Sentry fails to install/run around 30% of the time when using sentrycli_cdnurl
#1758
Comments
sentrycli_cdnurl
1sentrycli_cdnurl
Thanks for the report. |
Can't install cli at all.
Increased npm config setting |
Can you try using PyPI instead of NPM? |
I've found the way around it: manually downloaded binaries and then set SENTRY_BINARY_PATH= alongside SENTRYCLI_SKIP_DOWNLOAD=1. |
@loewenheim, thank you for the suggestion. Why don't I try it before? Likely because I am stupid :) |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Still seeing this quite often unfortunately. |
Environment
Jenkins
Using @sentry/next
Using artifactory (changing the URL with
sentrycli_cdnurl
)Steps to Reproduce
Around 30% of our builds fail with:
Error: Unexpected sentry-cli version "", expected "1.75.2"
I suspect it's because we're altering the download location with
sentrycli_cdnurl
, however, I don't think artifactory is the issue as all our other dependencies (including a few others with binaries) install without issue. Seems like a race condition somewhere.Expected/Actual Result
The package would install and run correctly.
Logs
The text was updated successfully, but these errors were encountered: