Repository navigation
Verify supported schema-2 history export bundles - #208
Merged
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
October 23, 2026 09:23
…ry-bundles # Conflicts: # CHANGELOG.md
|
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.
The published reader rejects valid schema-2 exports and computes different canonical integrity bytes for Unicode and several finite-float forms. Support schema 1 and 2, validate schema-2 lossless Avro memo authority/projection/redaction, and match the existing PHP
json-recursive-ksort-v1representation. Unknown/malformed versions, invalid memo data, bad checksums and invalid signatures still refuse.Addresses #173. Four genuine unmodified waiting/completed exports from published Server 2.9.7 / Core 2.7.2 include an independent Unicode cohort. All 615 loaded Core files match the immutable release. Exact raw-file hashes and canonical checksums are committed. These are fresh confirming cohorts; Website #320's earlier raw files were retired and are not recreated or relabeled. A separate 532-vector published PHP reference and explicitly synthetic signed-Unicode control qualify the encoding. Schema-1's producer uses the same canonical flags/order; valid legacy support remains.
Current candidate
5e42994aincludes merged4c79bc49and passes 269 combined verifier/TLS/metrics/harness/backoff controls, Ruff and mypy on 37 files. Functional parent22b20ddfull: 3,273 pass / two skips / 105 integration deselections, 116.04 seconds. Tests-first source retains 20/11 and later canonical 6/30 fail/pass results. Earlier parent1a02a48full had two unchanged process-readiness timeouts; that failure remains recorded independently. Current exact-head hosted gates/analyzer readbacks are pending; no guard was relaxed.Two separate actual fractional-zero producer-invalid exports are retained as negative controls. PHP's verifier/CLI and Python must reject them; Core #912 owns the producer follow-through. #190's older/native context stays open independently. Clean bundle simulation still has zero replay checks and recommends only
review_before_promote.Guidance explicitly marks this behavior unreleased. Publication and normally installed console acceptance remain after #197 Trusted Publisher setup. No version/tag, runtime deadline, protocol floor, Core/Server/native/frozen or Cloud change is included.