Repository navigation
Reflect the registry's TrainingProvenanceRecord support - #2
Merged
Merged
Conversation
The registry accepts the training record since sourcelume-registry#15 (verified live: /records/validate conforms, the record is stored as sourcelume_model VALIDATED). The README table now marks the registry validate/publish step as working, with the direct curl call. The Python plugin still rejects the record client-side (it models only ProvenanceRecord), so that row stays expected-to-fail and the Makefile fallback messages name the actual cause. Apache-ai: Yes Generated-by: pi (claude-sonnet-5-5) Reviewed-by: anierbeck
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 registry accepts the training record since apache/sourcelume-registry#15. This updates the README and the Makefile messages to match.
curlcall.ProvenanceRecordand rejects the record client-side.Testing
Against a registry built from
main(with #15) and a local Atlas:POST /records/validatewithmodel/provenance-record.jsonreturns 200{"conforms": true, "issues": []}(before: 422).GET /records/{id}fortiny-lm-v1returnsTrainingProvenanceRecord,VALIDATED, stored assourcelume_model.make registry-validate: dataset record passes; model record fails in the plugin with the new message.Apache-ai: Yes
Generated-by: pi (claude-sonnet-5-5)
Reviewed-by: anierbeck