fix(issue summary): Add locking mechanism

[roaga]

If a summary is in progress for an issue while another request comes in, the other request should wait for a bit first. This ensures only one call to Seer per issue at a time.

[codecov]

Codecov Report

Attention: Patch coverage is 94.50549% with 5 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/seer/issue_summary.py	89.28%	3 Missing ⚠️
tests/sentry/seer/test_issue_summary.py	96.82%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #90347      +/-   ##
==========================================
- Coverage   87.78%   87.41%   -0.37%     
==========================================
  Files       10264    10273       +9     
  Lines      580241   585145    +4904     
  Branches    22635    22659      +24     
==========================================
+ Hits       509346   511504    +2158     
- Misses      70460    73203    +2743     
- Partials      435      438       +3     

[jennmueng]

other than the comments not making sense, seems reasonble to me.

Have you tested this extensively locally? Just want to make sure to not cause an issue summary INC...

[roaga]

@jennmueng fixed the comments and made it a bit more readable

My testing is:

• unit tests that should test the race conditions
• running summaries from the frontend locally

idk if that's enough 🤷

[jennmueng]

I'd say just making sure the locking mechanism works locally should suffice.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ HTTPError: 503 Server Error: Service Unavailable for url: http://seer-web-autofix/v1/automation/summarize/issue /api/0/organizations/{organization_id_or_slug}/... View Issue

_{Did you find this useful? React with a 👍 or 👎}