perf: remove extra refresh #789
Merged
Conversation
This file contains 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
This re-does part of #776 (that was reverted) It aims to reduce 1 DB operation by not refreshing immediately after changing a Session object. And to make the code style more similar to what we use elsewhere (not accessing the tables directly unless necessary)
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #789 +/- ##
==========================================
- Coverage 98.03% 98.03% -0.01%
==========================================
Files 442 442
Lines 36601 36600 -1
==========================================
- Hits 35882 35881 -1
Misses 719 719
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅ @@ Coverage Diff @@
## main #789 +/- ##
==========================================
- Coverage 98.03% 98.03% -0.01%
==========================================
Files 442 442
Lines 36601 36600 -1
==========================================
- Hits 35882 35881 -1
Misses 719 719
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. @@ Coverage Diff @@
## main #789 +/- ##
==========================================
- Coverage 98.03% 98.03% -0.01%
==========================================
Files 442 442
Lines 36601 36600 -1
==========================================
- Hits 35882 35881 -1
Misses 719 719
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. @@ Coverage Diff @@
## main #789 +/- ##
==========================================
- Coverage 98.03% 98.03% -0.01%
==========================================
Files 442 442
Lines 36601 36600 -1
==========================================
- Hits 35882 35881 -1
Misses 719 719
Flags with carried forward coverage won't be shown. Click here to find out more.
|
adrian-codecov
approved these changes
Oct 15, 2024
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 re-does part of #776 (that was reverted)
It aims to reduce 1 DB operation by not refreshing immediately after changing a Session object.
And to make the code style more similar to what we use elsewhere (not accessing the tables directly unless necessary)
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.