You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On adding a tag to an annotation of an immutable object such as a YAMCS telemetry plot, I'm seeing an increasing number of redundant requests made to the provider.
Expected vs Current Behavior
Expected:
at most 2 - 4 requests made to providers (CouchDB) upon adding a tag to an annotation
Current:
an increasing number of requests made depending on how many annotations you've looked at so far
Steps to Reproduce
Start Open MCT with YAMCS quickstart
Navigate to yamcs telemetry, make a few annotations on the plot and add some tags
Refresh the page and open the network tab in devtools. Set it to filter Fetch/XHR only
Click on an existing annotation and add a tag. Observe there are only 2 _find requests being made
Click on a bunch of the other existing annotations
Create a new annotation and add a tag
Observe an increased number of _find requests being made in the inspector
Environment
Open MCT Version: 2.2.3
Deployment Type: openmct-yamcs quickstart
OS: MacOS
Browser: Chrome (any)
Impact Check List
Data loss or misrepresented data?
Regression? Did this used to work or has it always been broken?
Is there a workaround available?
Does this impact a critical component?
Is this just a visual bug with no functional impact?
Does this block the execution of e2e tests?
Does this have an impact on Performance?
Additional Information
Screen.Recording.2023-05-23.at.10.26.47.AM.mov
The text was updated successfully, but these errors were encountered:
Summary
On adding a tag to an annotation of an immutable object such as a YAMCS telemetry plot, I'm seeing an increasing number of redundant requests made to the provider.
Expected vs Current Behavior
Expected:
Current:
Steps to Reproduce
_find
requests being made_find
requests being made in the inspectorEnvironment
Impact Check List
Additional Information
Screen.Recording.2023-05-23.at.10.26.47.AM.mov
The text was updated successfully, but these errors were encountered: