Skip to content

fix(bench): send bearer auth for keyed decode runs - #136

Merged
plotarmordev merged 5 commits into
MiaAI-Lab:mainfrom
rksharma-owg:codex/bench-decode-auth
Sep 12, 2026
Merged

plotarmordev merged 5 commits into
MiaAI-Lab:mainfrom
rksharma-owg:codex/bench-decode-auth

Conversation

@rksharma-owg

Copy link
Copy Markdown
Contributor

Summary

Closes #117. tests/bench_decode.py now sends Authorization: Bearer <key> when API_KEY or the documented VLLM_API_KEY environment variable is set. This makes the decode benchmark usable against keyed /v1 serves.

The change is transport-only: prompts, timing, token calculations, and speculative-decoding accounting are unchanged. /health and /metrics remain unchanged because the README documents those endpoints as unguarded.

Testing

  • python3 tests/test_bench_decode_auth.py
  • python3 -m py_compile tests/bench_decode.py tests/test_bench_decode_auth.py
  • python3 tests/test_bringup_robustness.py
  • python3 tests/test_numeric_config.py
  • python3 tests/test_start_overrides.py
  • python3 tests/test_suppress_stops.py
  • python3 tests/test_warm_restart_stdout.py
  • git diff --check

No live 2-node DGX Spark run was performed because this workspace does not have the target hardware.

Checklist

  • I have read the README and kept the change consistent with it.
  • The change is reproducible and locally verified.
  • Existing defaults and unauthenticated serves remain unchanged.
  • No new configuration knob or README behavior change is required.
  • The PR description includes the exact validation commands and hardware limitation.

@plotarmordev plotarmordev added the triage/P2 Community triage 2026-09-09: useful scoped work, schedule after P0/P1 label Sep 9, 2026
d7dd7de raised the shipped per-prompt image cap from 4 to 100 in start.sh,
start-tp4.sh, .env.example and three README references, but the filer-facing
hint block in .github/ISSUE_TEMPLATE/1_bug.md was missed.

This is the only tracked site left saying 4 (git grep 'image:4' returns this
line and nothing else) and it contradicts README:198/380/692, .env.example:162,
start.sh:180 and start-tp4.sh:230. It sits in the text a reporter reads while
deciding what to check, so it re-seeds the confusion the raised default was
meant to remove: the cap is a copy-once .env value (start.sh:52), so an
operator whose .env still pins 4 is told here that 4 is current and reads the
mismatch as a server fault rather than a local config value. The boot log
already prints the effective value (start.sh:1184).

Comment-only change: no knob, script behaviour, default or measured number
changes, and nothing is executed on either node.
@plotarmordev plotarmordev added P2 Important scoped work; schedule after P0 and P1 and removed triage/P2 Community triage 2026-09-09: useful scoped work, schedule after P0/P1 labels Sep 12, 2026
@plotarmordev

Copy link
Copy Markdown
Collaborator

Maintainer follow-up before merge: Retain the transport-only bearer-auth change, add loopback HTTP coverage for key precedence/empty values and keyless health/metrics, and document the precedence contract.

Applying normal follow-up/prerequisite commits, preserving the original PR ancestry without a force push. Prepared exact head: 5f2db3d0e1d77b38e183eafa7b50e523d29b6a3f. Focused checks passed: python tests/test_bench_decode_auth.py. The final head also passed the secret/content gates; independent HELP review checked the corrected scope. No deployment-local files or live-run artifacts are included.

@plotarmordev plotarmordev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving exact corrected head 5f2db3d0e1d77b38e183eafa7b50e523d29b6a3f after independent HELP review and the focused checks recorded above. Retain the transport-only bearer-auth change, add loopback HTTP coverage for key precedence/empty values and keyless health/metrics, and document the precedence contract.

Proceeding with a normal, head-pinned merge. No hosted checks are configured/reported; local results are not being represented as hosted CI. No new GPU or performance qualification is claimed. Follow-up: run merged-branch hosted validation when CI becomes available.

@plotarmordev
plotarmordev merged commit 70001f1 into MiaAI-Lab:main Sep 12, 2026
@plotarmordev plotarmordev added the reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification. label Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P2 Important scoped work; schedule after P0 and P1 reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tests/bench_decode.py sends no Authorization header: 401 on every request when VLLM_API_KEY is set

3 participants