From dd31e6fd23ccc80c4854ecd52f0f6fb42bdcc997 Mon Sep 17 00:00:00 2001 From: kiryazovi-redis Date: Sat, 18 Jul 2026 18:17:23 +0300 Subject: [PATCH] test(search): skip TestSearchLimitOffset on RESP3 for standalone too FT.SEARCH on RESP3 ignores the LIMIT offset server-side (RediSearch#10369), returning [0, offset+count) instead of [offset, offset+count). The existing skip only covered cluster+RESP3, but the same module behaviour reproduces on a standalone Redis Enterprise database, so TestSearchLimitOffset(standalone,Resp3) fails 10/10. Broaden the skip to all RESP3 runs (cluster and standalone) until the module bug is resolved; standalone+RESP3 offset behaviour still needs module-team confirmation. --- tests/NRedisStack.Tests/Search/SearchTests.cs | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tests/NRedisStack.Tests/Search/SearchTests.cs b/tests/NRedisStack.Tests/Search/SearchTests.cs index 2ce2ddbf..55de7722 100644 --- a/tests/NRedisStack.Tests/Search/SearchTests.cs +++ b/tests/NRedisStack.Tests/Search/SearchTests.cs @@ -78,12 +78,13 @@ public void TestSearchLimitOffset(string endpointId) { SkipClusterPre8(endpointId); - // Cluster + RESP3 ignores the LIMIT offset server-side: FT.SEARCH returns the window + // RESP3 ignores the LIMIT offset server-side: FT.SEARCH returns the window // [0, offset+count) instead of [offset, offset+count). This is a RediSearch module bug, - // not a client bug (the raw wire reply already contains the wrong documents); skip until fixed. + // not a client bug (the raw wire reply already contains the wrong documents). It reproduces + // on both cluster and standalone Redis Enterprise databases, so skip both until fixed. // https://github.com/RediSearch/RediSearch/issues/10369 - Assert.SkipWhen(endpointId == EndpointsFixture.Env.Cluster && TestContext.Current.GetRunProtocol().IsResp3(), - "RediSearch#10369: FT.SEARCH on cluster+RESP3 ignores the LIMIT offset"); + Assert.SkipWhen(TestContext.Current.GetRunProtocol().IsResp3(), + "RediSearch#10369: FT.SEARCH on RESP3 ignores the LIMIT offset (cluster and standalone)"); IDatabase db = GetCleanDatabase(endpointId); var ft = db.FT();