Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

fix: LSDV-5526: Fix duplication of classifications in LLM scenario #1535

Merged
merged 10 commits into from
Sep 8, 2023

Conversation

Gondragos
Copy link
Contributor

@Gondragos Gondragos commented Aug 22, 2023

This PR should fix some issues in existed LLM scenario such as:

  • After editing text and with a successful response, textarea doesn't get replaced (it also causes areas duplication)
  • Getting errors from ml-backend breaks the current regions state

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
  • Frontend

What does this fix?

It fixes areas duplication and stop from making any changes in region and suggestion lists if we get null instead of new suggestion list.

What libraries were added/updated?

N/A

Does this change affect performance?

Nope

Does this change affect security?

Nope

What alternative approaches were there?

The alternative approach could be provided in the context of another tasks when we get understanding of what it should be.

What feature flags were used to cover this change?

fflag_feat_all_lsdv_e_294_llm_annotations_180723_long

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)

Enabling flag_feat_all_lsdv_e_294_llm_annotations_180723_long could break the previous scenarios used smart tools for Image Segmentation.

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

Auto Annotating, TextArea

@codecov-commenter
Copy link

codecov-commenter commented Aug 22, 2023

Codecov Report

Patch coverage is 71.87% of modified lines.

Files Changed Coverage
src/regions/Area.js ø
src/regions/KeyPointRegion.js 0.00%
src/mixins/KonvaRegion.js 50.00%
src/components/ImageView/ImageView.js 76.92%
src/stores/Annotation/Annotation.js 81.81%
src/regions/AliveRegion.tsx 100.00%
src/regions/BrushRegion.js 100.00%
src/utils/feature-flags.ts 100.00%

📢 Thoughts on this report? Let us know!.

area.store.loadSuggestions(new Promise((resolve) => setTimeout(() => {
resolve(suggestions);
}, 1000)), x => x);
}, 1000);
Copy link
Collaborator

Choose a reason for hiding this comment

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

why so long? can we reduce it to make it go faster?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We surely can, but I don't know if it catch the problem when it appears.

@Gondragos Gondragos merged commit 1526719 into master Sep 8, 2023
14 checks passed
@Gondragos Gondragos deleted the fb-lsdv-5526/llm-interactive-fix branch September 8, 2023 00:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants