Skip to content

fix(worker): Handle TorngitServerUnreachableError during commit update#815

Open
sentry[bot] wants to merge 1 commit intomainfrom
seer/fix/handle-torngit-unreachable-error
Open

fix(worker): Handle TorngitServerUnreachableError during commit update#815
sentry[bot] wants to merge 1 commit intomainfrom
seer/fix/handle-torngit-unreachable-error

Conversation

@sentry
Copy link
Copy Markdown
Contributor

@sentry sentry bot commented Apr 15, 2026

Fixes WORKER-Y7K. The issue was that: Bitbucket API read timeout during ancestor tree fetch caused unhandled TorngitServerUnreachableError due to insufficient timeout resilience.

  • Imported TorngitServerUnreachableError exception.
  • Added error handling for TorngitServerUnreachableError when updating commit information.
  • Logs a warning and returns False if the Git provider is unreachable during the commit update process.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 13322269

Not quite right? Click here to continue debugging with Seer.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.


Note

Low Risk
Low risk: small change limited to exception handling and logging when fetching commit details from a Git provider times out or is unreachable.

Overview
Prevents unhandled failures during commit metadata backfill by catching TorngitServerUnreachableError in possibly_update_commit_from_provider_info.

When the provider can’t be reached, the worker now logs a warning (with stack trace) and returns False instead of erroring out.

Reviewed by Cursor Bugbot for commit 99df8e5. Bugbot is set up for automated code reviews on this repo. Configure here.

@sentry
Copy link
Copy Markdown
Contributor Author

sentry bot commented Apr 15, 2026

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.25%. Comparing base (8c332b1) to head (99df8e5).
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
apps/worker/services/repository.py 33.33% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #815      +/-   ##
==========================================
- Coverage   92.25%   92.25%   -0.01%     
==========================================
  Files        1306     1306              
  Lines       48004    48007       +3     
  Branches     1636     1636              
==========================================
+ Hits        44286    44287       +1     
- Misses       3407     3409       +2     
  Partials      311      311              
Flag Coverage Δ
workerintegration 58.57% <33.33%> (-0.01%) ⬇️
workerunit 90.37% <0.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@codecov-notifications
Copy link
Copy Markdown

codecov-notifications bot commented Apr 15, 2026

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
apps/worker/services/repository.py 33.33% 2 Missing ⚠️

📢 Thoughts on this report? Let us know!

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 this pull request may close these issues.

0 participants