chore: release v0.2.0 + live vendor-API smoke checks#4
Merged
Conversation
Cuts v0.2.0 (bundles the merged contributor work: vast v0->v1 instances fix #1, --gpu offer steering #2, download progress in status #3) and adds a live smoke-check for the one failure class the mocked suite can't catch: an upstream vendor deprecating an endpoint (as in #1, where vast's v0 instance list began returning HTTP 410). - tests/test_live.py: @pytest.mark.live probes of the real vast/runpod/HF endpoints aiod depends on. Excluded from the default run (addopts -m "not live") so `pytest tests/` stays hermetic; run via `pytest -m live`. - .github/workflows/smoke.yml: weekly + manual. Auth-free probes (runpod pricing, HF sizing) need no secrets; vast/runpod authed probes run only if VAST_API_KEY/RUNPOD_API_KEY repo secrets are set. Never runs on pull_request, so fork PRs can't reach secrets. Opens an issue on failure. - pyproject: register + default-exclude the `live` marker; bump 0.1.0 -> 0.2.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Cuts v0.2.0 and adds a live smoke-check for the one failure class the mocked unit suite can't catch — an upstream vendor deprecating an endpoint (PR #1 was exactly this: vast's v0 instance list started returning HTTP 410).
What's in v0.2.0
auth_errorkey detection (fix: vast deprecated /api/v0/instances/ list endpoint (410) #1)--gpuoffer steering (feat: --gpu flag to steer offer search toward specific hardware #2)aiod status(fix vast v1 API + show download progress in aiod status #3)Smoke-check
tests/test_live.py—@pytest.mark.liveprobes of the real vast/runpod/HF endpoints aiod depends on. Excluded from the default run (addopts -m "not live") sopytest tests/stays hermetic; run viapytest -m live..github/workflows/smoke.yml— weekly + manual. Auth-free probes (runpod pricing, HF sizing) need no secrets; the vast/runpod authenticated probes only run ifVAST_API_KEY/RUNPOD_API_KEYare added as repo Actions secrets. Never runs onpull_requestso fork PRs can't reach secrets. Opens an issue on failure.Local:
pytest tests/→ 64 passed, 5 live deselected;pytest -m live→ vast v1 + bundles + runpod GraphQL + HF all green.