Repository navigation
fix: doctor no longer fails CI over a missing store library; messages name the package - #44
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…install Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
It failed compare -- and so every GitHub Action run -- for a config that names captures.store, although a run on a committed suite never reads the bucket. The capture commands that need the library still exit 1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er fails, over it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cs pages - captures/remote.py: open_store()'s Raises: line for RemoteStoreUnavailable was 231 characters; wrap it to the file's ~100-column style. - test_docs_currency.py: _INSTALL_COPY_FILES was missing docs/getting-started.md and docs/agents.md. Both exist and currently contain none of RETIRED_INSTALL_TERMS; add them so a regression there is caught. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6 tasks done
…SINK on SDK 0.5.0) Matches the SDK rename in evalshift-sdk#15, so the bucket has one name on both sides: EVALSHIFT_CAPTURE_STORE in the agent's environment and captures.store in evalshift.yaml. Version notes say which SDK reads which name. Also drops a leftover 'optional extras' phrase in sdk.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolves the CHANGELOG [Unreleased] conflict with #43: both Fixed entries kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
babaliauskas
added a commit
that referenced
this pull request
Oct 10, 2026
Resolves the conflicts with #44 (store library messages, doctor warns): - doctor.py docstring and DOCS.md/llms-full.txt doctor text: exit 1 only on an invalid config or a blocking semantic/llm_judge model without a key; a missing store library is now a warning, naming the package. - llms-full.txt doctor rows: #44's captures.store row plus this branch's evaluator keys row. - CHANGELOG [Unreleased]: both branches' Added/Changed/Fixed entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
babaliauskas
added a commit
that referenced
this pull request
Oct 10, 2026
Resolves the conflicts with #44 and #45: - DOCS.md captures-store paragraph: main's package-name install wording (pip install boto3 / google-cloud-storage / azure-storage-blob azure-identity) plus this branch's capture sync --repair re-fetch clause. - CHANGELOG [Unreleased]: this branch's Added/Fixed entries merged with main's Added/Changed/Fixed entries from #43, #44 and #45. Co-Authored-By: Claude Opus 5.5 <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
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.
Summary
Companion to evalshift/evalshift-sdk#15. Two problems with
captures.storein 1.3.0:doctor'scaptures.storerow returnedfailwhen the store's client library was missing,compareexits 1 on any doctorfail, and the GitHub Action installs the bareevalshiftpackage, so every Action run for a config namingcaptures.storewent red, although a run on a committed suite never reads the bucket. The row now warns, naming the package to install.capture fetch/list/sync, which do need the library, still exit 1.pip install boto3/google-cloud-storage/azure-storage-blob azure-identity(both Azure packages in one command). The[s3]/[gcs]/[azure]extras still exist but are no longer documented. The scheme → module → package tables are byte-identical to the SDK's.Also in this branch:
EVALSHIFT_CAPTURE_STORE(feat: an unusable EVALSHIFT_SINK raises at startup; messages name the package, not the extra evalshift-sdk#15), so the bucket has one name on both sides; the docs say SDK 0.5.0 readsEVALSHIFT_SINK, which keeps working on newer SDKs too.doctorreference, bucket paragraph), llms-full.txt (five blocks incl. the exit-code bullet), docs/configuration.md (capturesInstall column), docs/sdk.md, CHANGELOGUnreleased(Fixed + Changed).test_copy_names_packages_not_extras) fails ifevalshift[s3]-style extras, "client extra" or "optional dependency" reappear in the prose files, docs/sdk.md, getting-started.md or agents.md.docs/superpowers/specs/2026-10-09-sink-dependency-loud-failure-design.md,docs/superpowers/plans/2026-10-09-sink-dependency-loud-failure.md.Release
Version is not bumped here. Ship as 1.3.1; the action's bump workflow then opens its pin PR. Independent of the SDK PR (no server or action change).
Verification
ruff check,ruff format --check,mypy --strict src/evalshift_cliclean;pytest -m "not integration"→ 2732 passed, coverage 95%; the pre-push CI mirror passed. Each task was reviewed individually and the whole branch (with the SDK PR) had a final review.🤖 Generated with Claude Code