Nine conformance vectors cannot be reissued by any key in the repository
I maintainer di solito rispondono entro 1 giorno
@lywinged ci sta già lavorando.
Dal 7/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What is wrong
Nine of the thirty action-receipt conformance vectors cannot be regenerated by anything in this repository. gen_rule_coverage_vectors.py records why in its own first paragraph: “The 01-09 fixtures pin a key whose private half is not published, so everything here pins its own deterministic test key.” The generator covers 10-30.
Until #171 they also passed the reproduction check, because that check copied the committed fixtures into its work directory before running the generator, so 01-09 were compared against copies of themselves and agreed every time. #171 empties the directory first and names the nine, with the reason, in NOT_GENERATED.
Spec section or file
examples/action-receipts/conformance/01-valid-controller-accepted.json through 09-unsupported-physical-completion.json, and examples/action-receipts/conformance/gen_rule_coverage_vectors.py.
Expected behavior
Every conformance vector reproducible from a key whose private half lives in the repository, which is the pattern gen_rule_coverage_vectors.py already uses for 10-30. Applied to 01-09, NOT_GENERATED empties and the reproduction guard needs no exemptions at all.
Impact
None on conformant implementations today. The nine are read on every run by tests/test_action_receipt_fixtures.py, which globs the whole directory and puts each vector through the verifier, signature included. They are verified; they are only unreproducible.
The cost is deferred rather than absent. A vector nobody can reissue has to be hand-edited every time the spec moves under it, and the first release that revises this corpus instead of adding to it turns all nine into hand edits at once, which is the class of silent divergence #171 exists to catch. #66 and #173 are building that release.
I have deliberately not touched them: reissuing changes pinned key material in vectors other implementations may pin, so the timing belongs to whichever release already touches these files. I am happy to do the mechanical work on request.
Related: #171, #66, #173
- Lingua principale
- Python
- Stelle
- 37
- Fork
- 33
- Merge medio
- 1g 4h
- PR unite (30g)
- 120
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di agentrust-io/trace-spec
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
agentrust-io/trace-spec#593 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs-review:HIGH
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
agentrust-io/trace-spec#591 · 11 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
prototype(manifest_requirements): resolve accepted_methods without duplicating bindings and reject unconfigured binding endpoints with ProfileErrorForse già presa @drk-ram l’ha presa 2 giorni fa. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 78/100
agentrust-io/trace-spec#580 ·
I maintainer di solito rispondono entro 1 giorno
-
feat(delegation): add parent_record_hash, verify_delegation_link, and verify_delegation_chain to agentrust_traceForse già presa @drk-ram l’ha presa 2 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 58/100
agentrust-io/trace-spec#581 ·
I maintainer di solito rispondono entro 1 giorno
-
revocation,trust-record-verify: implement es256 and es384 bundle verification and add EC revocation vectors (#448 items 1, 10)Forse già presa @drk-ram l’ha presa 2 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
agentrust-io/trace-spec#584 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di agentrust-io/trace-spec
Issue simili
-
follow-up
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
Download helper still uses huggingface_hub arguments removed in 1.0: USE_SYMLINKS is silently ignored and every download ends with a WinError 3 lineForse già presa @li-lizhe l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
IPv6 node addresses produce an invalid request URLForse già presa @RaphaelFakhri l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
typesense/typesense-python#154 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
elastic/elasticsearch-py#3592 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
developmentseed/titiler-cmr#250 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno