Fix CI - updated FT.INFO changes vector_index_sz_mb#503
Merged
Conversation
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
Collaborator
Author
|
This perceived server change may be reverted. I'm that case: we'll close this without merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This value is no longer zero, so the test expectation changes; to avoid version hell, just log for now
Note
Low Risk
Test-only relaxation of a version-sensitive assertion; no production code or API behavior changes.
Overview
Fixes CI failures after FT.INFO started reporting non-zero
vector_index_sz_mb(mapped toVectorIndexSzMebibytes).In four standalone
FT.INFOassertion blocks insideSearchTests(Alter/AlterAdd sync and async paths), the hardAssert.Equal(0, info.VectorIndexSzMebibytes)is removed and replaced withlog.WriteLineso the value is visible in test output without pinning it to a specific Redis/RediSearch version.Reviewed by Cursor Bugbot for commit 92b552c. Bugbot is set up for automated code reviews on this repo. Configure here.