-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Bust Symbolicator list_files
cache on uploads
#53049
Conversation
By attaching a random querystring parameter to the Sentry internal source, this will cause a cache miss in Symbolicators `list_files` cache, thus fetching and discovering the uploaded debug file immediately.
Does the altered URL have any effect on how e.g. object candidates are displayed? Or in other words, is this URL visible to users anywhere? |
I double-checked, and the URL is never exposed to users, and also not used for caching of downloaded files, but just for caching of Downloaded file caches and candidates are only using the |
Nice. Then I would just like to request comments somewhere in the code explaining what this query parameter is for, so that we can still understand this in a few years 😅 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #53049 +/- ##
==========================================
- Coverage 79.47% 77.78% -1.69%
==========================================
Files 4936 4934 -2
Lines 207488 207474 -14
Branches 35423 35429 +6
==========================================
- Hits 164892 161379 -3513
- Misses 37565 41058 +3493
- Partials 5031 5037 +6
|
PR reverted: 6faec71 |
This reverts commit 99b7d19. Co-authored-by: Swatinem <580492+Swatinem@users.noreply.github.com>
Reverting because the PR hardcodes the |
By attaching a random querystring parameter to the Sentry internal source, this will cause a cache miss in Symbolicators
list_files
cache, thus fetching and discovering the uploaded debug file immediately.This is very similar to
bump_reprocessing_revision
, except it has a TTL. Also the code forbump_reprocessing_revision
is overly complex for reasons I don’t understand so I don’t want to touch that.I tested this with a local symbolicator that has caching turned on, see this comment:
sentry/tests/symbolicator/test_minidump_full.py
Lines 156 to 160 in 3eae808