Repository navigation
fix(benchmark): secure maintained offline reproduction without rewriting history (#89) - #106
Merged
Merged
Conversation
added 2 commits
November 4, 2026 14:07
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.
The archived reranker requirements triggered eight security alerts, and dependency bot PRs #85/#86 would rewrite the dependency identity of old measurements. This adds a separate maintained offline ONNX reproduction path, preserves every historical file, and documents all eight advisory dispositions.
The benchmark-only runner reuses the unchanged installed
OnnxRanker, verifies/stages the three original ONNX model/tokenizer identities, requires hash-pinned runtime versions, and refuses Transformers, setuptools, Torch and custom-code v3.5 before loading. An owned child bounds native inference; exclusive output directories retain partial successes, failures and unattempted cases. No model download, production profile change, SQL change or data rewrite is introduced.Release 0.6.32 includes the required metadata and source-version compatibility labels. The operator guide covers isolated wheel rebuild, retained failures, dependency upgrades and code-environment rollback.
Validation:
The full suite was not repeated for this benchmark-only addition and mechanical release labels. Raw observations, terminal results, package/source/model identities and independent reviews are published under
docs/benchmarks/maintained-rerankers/verification/.The historical four-model protocol remains failed (2,338 actual / 2,688 prescribed; 350 unattempted v3.5 observations). This does not claim v3.5 compatibility, pretrained-model quality/performance, or production deployment. Eight alerts attached to preserved archival requirements can remain visible; no advisory was dismissed or hidden. Supersede #85/#86 after this replacement merges rather than editing the frozen file.
Closes #89.
Next, separately: #83 measured BGE versus Jina v5 omni small/nano comparison using existing model-bound generation workflows; no production embedding cutover is authorized by this PR.