-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix: apply notify task after lock is released #265
Conversation
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 #265 +/- ##
=======================================
Coverage 97.65% 97.65%
=======================================
Files 424 424
Lines 33532 33536 +4
=======================================
+ Hits 32746 32750 +4
Misses 786 786
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 Additional details and impacted files@@ Coverage Diff @@
## main #265 +/- ##
=======================================
Coverage 97.64% 97.64%
=======================================
Files 393 393
Lines 32832 32836 +4
=======================================
+ Hits 32058 32062 +4
Misses 774 774
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 #265 +/- ##
=======================================
Coverage 97.64% 97.64%
=======================================
Files 393 393
Lines 32832 32836 +4
=======================================
+ Hits 32058 32062 +4
Misses 774 774
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 #265 +/- ##
=======================================
Coverage 97.64% 97.64%
=======================================
Files 393 393
Lines 32832 32836 +4
=======================================
+ Hits 32058 32062 +4
Misses 774 774
Flags with carried forward coverage won't be shown. Click here to find out more.
|
0eea563
to
17d9a0e
Compare
There's 1 more change I'd like to see in this PR, which is changing
to be
You see, that is when the notification task realizes that there's possibly another notification task happening. However when line 87 was changed to use So we should handle the exception better. |
c63cdb3
to
fc7af92
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving on the basis that the other change I commented on has nothing to do with these changes so should probably be on another PR.
This seems fine. Apologies for suggesting unrelated changes 😅
0469f50
to
27899c1
Compare
there is the possibility of an issue when the notify task is queued up before the test result finisher releases the notification lock due to the fact that a notify will drop itself if it fails to lock, so we should make sure that the test result finisher is not holding the notification lock before it queues up the notify task Signed-off-by: joseph-sentry <[email protected]>
Signed-off-by: joseph-sentry <[email protected]>
27899c1
to
3d4a3bc
Compare
there is the possibility of an issue when the
notify task is queued up before the test result finisher releases the notification lock due to the fact that a notify will drop itself if it fails to lock, so we should make sure that the test result finisher is not holding the notification lock before it queues up the notify task
Sentry Issue
Fixes: https://github.com/codecov/internal-issues/issues/364