fix: LSDV-2775: fix predictions selector in next task with ML backend model version #4363
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
… model version dropdown
✅ Deploy Preview for label-studio-docs-new-theme ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for heartex-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
/git merge develop
|
bmartel
approved these changes
Jul 13, 2023
bmartel
requested changes
Jul 13, 2023
There was a problem hiding this comment.
Test fails on CI https://github.com/heartexlabs/label-studio/actions/runs/5534708309/jobs/10100011661#step:13:1169, looks good otherwise though. Seems like there is no ml_backend set.
…changes and auto-update feature selection
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #4363 +/- ##
===========================================
+ Coverage 75.65% 75.69% +0.03%
===========================================
Files 156 156
Lines 12299 12316 +17
===========================================
+ Hits 9305 9322 +17
Misses 2994 2994 ☔ View full report in Codecov by Sentry. |
bmartel
approved these changes
Jul 14, 2023
shayantabatabaee
pushed a commit
to shayantabatabaee/label-studio
that referenced
this pull request
Sep 19, 2023
… model version (HumanSignal#4363) * fix: LSDV-2775: fix predictions selector in next task with ML backend model version dropdown * Add ml backend test for auto update enabled/disabled * feat: LSDV-5386: update ml model documenation to support model setup changes and auto-update feature selection * Fix missing mock endpoint --------- Co-authored-by: nik <nik@heartex.net> Co-authored-by: farioas <farioas@users.noreply.github.com> Co-authored-by: andreasdivaris <dredivaris@gmail.com>
16 tasks
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.
… model version dropdown
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change madeex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errorsChange has impacts in these area(s)
(check all that apply)
Describe the reason for change
(link to issue, supportive screenshots etc.)
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.)