Skip to content
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

Allow opt-out from release artifact deduplication via checksum #1322

Closed
joebeachjoebeach opened this issue Sep 7, 2022 · 2 comments · Fixed by #1334
Closed

Allow opt-out from release artifact deduplication via checksum #1322

joebeachjoebeach opened this issue Sep 7, 2022 · 2 comments · Fixed by #1334

Comments

@joebeachjoebeach
Copy link

When upgrading @sentry/cli from 2.3.1 to 2.4.0 (and higher), my organization ran into an issue. Our sourcemap uploads began failing with 429 status codes, indicating that we were exceeding our request quota. After doing some digging, I've determined that the feature to use checksums to dedupe uploaded release artifacts is ultimately responsible for this. For every artifact we upload, the CLI is now issuing an extra API request for the deduplication attempt. Our request count is effectively doubled, and we're now exceeding the quota. This means we're unable to adopt any @sentry/cli version beyond 2.3.1 at the moment.

Would it be possible to make that deduplication attempt configurable so that it could be opted out of?

@kamilogorek
Copy link
Contributor

Would it be possible to make that deduplication attempt configurable so that it could be opted out of?

Done :)

@joebeachjoebeach
Copy link
Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants