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
When deleting characters in a search query while using CouchDB, sometimes a conflict error can be seen in the network tab of a PUT request against 'mine' (My Items folder).
This is caused by the myItemsInterceptor being triggered (this creates the 'My Items' folder if it doesn't already exist on startup) because a domainObject is being returned as undefined from an aborted CouchObjectProvider.get() request.
Expected vs Current Behavior
We should handle the case of aborted requests returning undefined domain objects
Steps to Reproduce
Start Open MCT w/ Couch DB (openmct-quickstart might be good for this)
In the Grand Search, search for something and let the request complete
With the network tab open, one-by-one, remove a letter. Make sure to trigger Aborts by removing it in the middle of requests.
See the conflict error in the console / network tab
If you don't see it, refresh and try again. It's only ever triggered once for some reason.
Environment
Open MCT Version: 3.3.0-next
Deployment Type: testathon
OS: any
Browser: 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
The text was updated successfully, but these errors were encountered:
Summary
When deleting characters in a search query while using CouchDB, sometimes a conflict error can be seen in the network tab of a PUT request against 'mine' (My Items folder).
This is caused by the
myItemsInterceptor
being triggered (this creates the 'My Items' folder if it doesn't already exist on startup) because adomainObject
is being returned asundefined
from an abortedCouchObjectProvider.get()
request.Expected vs Current Behavior
We should handle the case of aborted requests returning
undefined
domain objectsSteps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: