Skip to content

Conversation

@niklub
Copy link
Collaborator

@niklub niklub commented Mar 6, 2024

PR fulfills these requirements

  • Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
  • Tests for the changes have been added/updated (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
  • Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

  • Product design
  • Backend (Database)
  • Backend (API)
  • Frontend

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)

  • Yes, and covered entirely by feature flag(s)
  • Yes, and covered partially by feature flag(s)
  • No
  • Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

@netlify
Copy link

netlify bot commented Mar 6, 2024

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit 911c1e3
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/65ef89c86726e50008798c10

@netlify
Copy link

netlify bot commented Mar 6, 2024

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit 911c1e3
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/65ef89c8812ac70008a3d717

@codecov
Copy link

codecov bot commented Mar 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.37%. Comparing base (40e174b) to head (911c1e3).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #5546      +/-   ##
===========================================
- Coverage    75.77%   75.37%   -0.41%     
===========================================
  Files          157      157              
  Lines        13125    13249     +124     
===========================================
+ Hits          9946     9986      +40     
- Misses        3179     3263      +84     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@niklub niklub force-pushed the fb-ml-backend-exp branch from 300824f to 4bbd435 Compare March 7, 2024 13:09
@niklub niklub changed the title Fb ml backend exp feat: HUMSIG-37: Enhancing ML backend connection experience Mar 7, 2024
@niklub niklub force-pushed the fb-ml-backend-exp branch from 12f300c to 9211b86 Compare March 7, 2024 17:00
@@ -0,0 +1,56 @@
.toggle-right
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicholasrq You mentioned SCSS is the way forward, how strongly are we taking that at this time with regards to new code? With Stylus having been long deprecated we are going to have to move all existing Stylus over to SCSS, and wanted to know if that is something we are trying to encourage in new PRs?

Copy link
Contributor

@bmartel bmartel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ran a formatter/linter on the other frontend files, pushed that up as well. Looks good overall now.

@niklub niklub merged commit b198728 into develop Mar 11, 2024
Comment on lines 660 to +673
def get_predictions(self, task):
project = task.project
if not project.show_collab_predictions:
return []
else:
for ml_backend in project.ml_backends.all():
ml_backend.predict_tasks([task])
return super().get_predictions(task)
""" """
predictions = task.get_predictions_for_prelabeling()
return PredictionSerializer(predictions, many=True, read_only=True, default=[], context=self.context).data

# def get_predictions(self, task):
# project = task.project

# if not project.show_collab_predictions:
# return []
# else:
# # for ml_backend in project.ml_backends.all():
# # ml_backend.predict_tasks([task])
# return super().get_predictions(task)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to make sure we didn't break anything with this change, and remove commented out code

'title': 'Retrieve Predictions',
'order': 90,
'dialog': {
'modal_title': 'Retrieve Predictions',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modal_title -> title

'dialog': {
'text': 'This action will create new annotations from predictions with the selected model version '
'for each selected task.',
'modal_title': 'Create Annotations From Predictions',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modal_title -> title

niklub pushed a commit that referenced this pull request Mar 12, 2024
niklub added a commit that referenced this pull request Mar 12, 2024
#5569)

Revert "feat: HUMSIG-37: Enhancing ML backend connection experience (#5546)"

This reverts commit b198728.

Co-authored-by: nik <nik@heartex.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants