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
**Issue:** `Throw if attempting to pause at a sequence number before the
latest summary` test was failing erratically. Passed for local server
but failed for odsp/frs etc services.
**Root Cause:** The test tries to check that the `loadContainerPaused()`
function should throw an error when we try to load from a seq number
which is lesser than the latest snapshot sequence number. This was
failing because the latest snapshot that the container refereed to was
an older one (the very first snapshot generated when a container is
created) because the`fetchSnapshot` races to retrieve the snapshot from
cache or network and in almost all cases, refers to the snapshot in
cache.
**Fix:** Now we are explicily providing the snapshot version number in
the `IRequestHeaders` so that the test refers to the latest snapshot
when performing comparisons.
[AB#8561](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/8561)
// Try to pause at sequence number 1 (before snapshot)
386
-
constsequenceNumber=1;
387
384
constheaders: IRequestHeader={
388
-
[LoaderHeader.loadMode]: {
389
-
opsBeforeReturn: "sequenceNumber",
390
-
},
385
+
// Force the container to load from the latest created summary instead of using the cached version. Latest snapshot is in cache is updated async so could cause test flakiness.
386
+
[LoaderHeader.version]: result.summaryVersion,
391
387
};
388
+
// Try to pause at sequence number 1 (before snapshot)
0 commit comments