-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Core
-
Release Notes Summary:Sequential requests are correctly handled.
-
Tags:
-
Backlog priority:900
-
Upgrade notes:
-
Sprint:nxfit 11.1.10, nxplatform 11.1.11, nxplatform 11.1.12
-
Story Points:1
Right now, for a given resource, if we perform two sequential requests, request A and request B, using the same resource, and the response of A arrives last because it took more time, we will end up getting obsolete information. We need to find a way to handle.
- causes
-
NXP-27644 Fix random failure on Browse Collection Web UI ftest
-
- Resolved
-
-
NXP-27764 Fix adding properties to documents during bulk import
-
- Resolved
-
- depends on
-
NXJS-188 Pass AbortSignal object to fetch API if any
-
- Resolved
-
- is related to
-
ELEMENTS-745 Fix tag creation on Nuxeo-selectivity
-
- Open
-
-
NXP-24966 Auto search behavior gives unexpected results
-
- Resolved
-
- is required by
-
NXP-25232 Auto-search in QuickSearch returns results in the wrong order
-
- Resolved
-