fix(worker): prevent OperationalError from expired ORM objects in UploadFinisher - #1866
Open
sentry[bot] wants to merge 1 commit into
Open
fix(worker): prevent OperationalError from expired ORM objects in UploadFinisher#1866sentry[bot] wants to merge 1 commit into
sentry[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1866 +/- ##
=======================================
Coverage 91.83% 91.83%
=======================================
Files 1332 1332
Lines 51830 51836 +6
Branches 1647 1647
=======================================
+ Hits 47598 47604 +6
Misses 3911 3911
Partials 321 321
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR addresses an
OperationalError: (psycopg2.OperationalError) server closed the connection unexpectedlyoccurring inapp.tasks.upload.UploadFinisher.Root Cause:
The
_handle_finisher_lockmethod inUploadFinisherperforms significant work, includingfinish_reports_processing. After this, it callsdb_session.commit()(line 597) to update the repository'supdatestamp. Due to SQLAlchemy's defaultexpire_on_commit=Truebehavior, all ORM objects in the session, including thecommitobject, are expired at this point.Immediately after the commit,
invalidate_cachesis called (line 609). Insideinvalidate_caches, accessing attributes likecommit.repoidtriggers a lazy-load from the database. If the PostgreSQL connection has been closed by the server (e.g., due to an idle timeout during the preceding long-running tasks), this lazy-load attempt results in theOperationalError.Solution:
To prevent accessing expired ORM objects on a potentially closed database connection, the necessary
commitandrepositoryattributes (such asrepoid,branch,commitid,repository.service,repository.author.username,repository.name,repository.branch) are now eagerly read and stored into local variables beforedb_session.commit()is called. Theinvalidate_cachesmethod has been refactored to accept these primitive values directly, eliminating any post-commit ORM attribute access that could trigger a lazy-load.Legal Boilerplate
Look, I get it. The entity doing business as "Codecov" is owned by Harness, Inc. In 2026 Harness acquired Codecov and as a result Harness 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 Harness can use, modify, copy, and redistribute my contributions, under Harness's choice of terms.
Fixes WORKER-Z5D