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: LSDV-5289-1: Load stats recalculation function from string, call after update task states #4676
Conversation
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
✅ Deploy Preview for heartex-docs canceled.
|
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #4676 +/- ##
===========================================
- Coverage 75.86% 75.85% -0.01%
===========================================
Files 157 157
Lines 12515 12531 +16
===========================================
+ Hits 9494 9505 +11
- Misses 3021 3026 +5 ☔ View full report in Codecov by Sentry. |
/git merge develop
|
…ialize-rq-jobs-deadlocks
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
… after update task states (HumanSignal#4676) * fix: LSDV-5289-1: move stats recalculation to string import * clarify log messages * fix confusing log message --------- Co-authored-by: jombooth <jombooth@users.noreply.github.com>
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
(link to issue, supportive screenshots etc.)
Attempt 2 at fixing deadlocks. Previously we were performing stats recalculation in parallel with updating task states in LSE.
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)