Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
HFCrossEncoderReranker.rank(..., return_score=True) returned reranked documents sorted by descending score, but the accompanying score array stayed in the original input order. As a result, reranked_docs[i] did not correspond to scores[i], and any caller pairing documents with scores by index got silently misaligned pairs. The bug was reported with a minimal reproduction and fixed upstream.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
This was a real bug and was fixed in redisvl v0.27.0. Upgrade to v0.27.0 or later so the returned scores align with the reranked documents. Source: https://github.com/redis/redis-vl-python/issues/693
Source: https://github.com/redis/redis-vl-python/issues/693
Fixes RedisVL HFCrossEncoderReranker returning scores in the original input order while documents come back reranked, silently misaligning doc/score pairs.
Fixes contract-review agents reporting the original liability cap when an amendment raised it and an order-form cap table overrode both.
Fixes a resume parser that invents a career gap because a margin-placed entry was read out of page order.