Repository navigation
test(grpc): run the interop lane against the manifest candidate - #314
Merged
Merged
Conversation
The live gRPC interop lane was hard-pinned to nightly-ff5f567, so the shipped FeatureService client was never exercised against the 2026.1 candidate. Pin SERVER_REVISION and SERVER_IMAGE to the server that honua-release platform-manifest.yaml selects (0e03bdd, index sha256:dcf3296f...). Seed and compose are fetched from that same revision. Refs #282
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
The live gRPC interop lane (
ci.ymlgrpc-interop,tests/grpc/conftest.py) was hard-pinned tonightly-ff5f567, so the shippedFeatureServiceclient never ran against the 2026.1 candidate. This was the SDKPY-003 gap in #282. This PR pinsSERVER_REVISIONandSERVER_IMAGEto the server that honua-releaseplatform-manifest.yaml(trunk62b8ecc) selects:0e03bdd06b3ca3fb1b82388110bb5dfa19b9f8fa, indexsha256:dcf3296f17a456a876c23133fae50b5b32628d4ec710e8bdab58f57d2394d750. The compose file and SQL seed are fetched from that same revision.Local evidence
docker buildx imagetools inspectof the pinned index listssha256:8a211f46bbc92fe6907b72fb8bcdc36a808924f3ca001a090591c0752360d2bdas its linux/amd64 child. Its revision label is0e03bdd.python -m pytest tests/grpc -q --run-integrationran from a clean Python 3.11 venv built from.github/requirements/ci.lockplus./packages/honua-sdk. Result: 4 passed in 246 s. The cases are sync/async unaryQueryFeaturesandQueryFeaturesStream, including pagination, metadata, attributes and geometry.This is lane evidence. It is not a release certification receipt.
What #282 still needs (not in this PR)
a4df654) fails at setup withgoverned requirements name another Python producer source. This SDK check is correct and fails closed. honua-release's requirements catalog (00e93d86, revision2026-10-17-complete.24, and still on trunk as2026-10-19-complete.25) namessource_revisions.sdk-python516c727. The manifest freezes5a79352(0.1.16). honua-releasetools/check_protocol_certification.pyapplies the same equality. honua-release#181 owns the fix, and open PR honua-release#767 moves the catalog to5a79352. After that merges,conformance/requirements-pins.jsonhere needs itssourceSha,requirementsRevisionand file SHA-256 pins moved to the merged commit.apply-editsneeds the operator-provisioned signed license (HONUA_CERTIFICATION_LICENSE_CONTENT).Refs #282