getsentry / getsentry/sentry

Race condition when uploading the same ProGuard mapping with different UUIDs concurrently

Open
#118,434 1 comment 1 reaction 1 assignee View on GitHub

@szokeasaurusrex is already working on this.

Since Jun 25, 2026.

Bug
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce
  1. Use sentry-cli proguard upload to upload the same proguard mapping twice, in parallel or in quick succession, but with different UUIDs set.

What is important here for reproducing the issue is that the second upload occurs while the initial upload is still assembling.

Expected Result

After the upload, both uploads (with both UUIDs) should be visible in Sentry.

Actual Result

The race condition can result in the case where only one of the UUIDs shows up in Sentry, the other one is forgotten.

The race condition is a bug in the implementation for https://github.com/getsentry/sentry/issues/106947. That bug fix does not handle the case where the initial upload is still assembling, only the case where the same mapping is uploaded after the initial mapping already exists.

Product Area

Other

Link

No response

DSN

No response

Version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.