Repository navigation
fix(benchmark): send Yandex privacy header - #312
Merged
Merged
Conversation
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.
Что исправлено
Benchmark runner для
LLM_PROVIDER=yandexтеперь передаётx-data-logging-enabled: falseчерез существующийextraHeaders. При наличииLLM_FOLDER_IDсохраняетсяx-folder-id. Для других OpenAI-compatible провайдеров privacy header автоматически не добавляется. Production gateway не менялся.Это узкая инфраструктурная подготовка #307 перед первым платным baseline-вызовом. Draft PR #311 не изменяется. Этот PR не закрывает #307.
Проверка
fetch; после исправления четыре варианта проходятmake lint-md,pnpm check(1032 tests, typecheck, build) иgit diff --check: успешноГраница дальнейшей квалификации
Исправление меняет фактический транспортный контракт benchmark. После merge потребуется новый clean SHA
mainдля baseline, повторная сверка prompt/schema fingerprints и configuration class, согласование Draft PR #311 с новым baseline, повторный plan mode и актуальное разрешение платного этапа. Исходный SHA9455a1ff67fa55b056e436777f8d9d9d120724d3не считается версией исправленного runner. Прежние результаты не становятся результатами нового запуска.