Skip to content

Name the parity oracle by its place inside PyMEOS rather than by this machine - #92

Merged
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/parity-oracle-identity-is-reproducible
Aug 28, 2026
Merged

Name the parity oracle by its place inside PyMEOS rather than by this machine#92
estebanzimanyi merged 1 commit into
MobilityDB:masterfrom
estebanzimanyi:fix/parity-oracle-identity-is-reproducible

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

The object-model parity artefact names its oracle by the place it occupies inside PyMEOS, pymeos/factory.py, which identifies the file being audited without carrying the checkout it happens to live in. A regression test asserts that one oracle read from two locations yields the same artefact.

An absolute path, as both of the report's exit points record, makes the same audit produce a different file from every checkout. A consumer that vendors the artefact and regenerates it to detect drift then reports drift that no change causes: MobilityAPI-Python's scheduled vendor-drift job compares a copy generated beside a developer's PyMEOS checkout against one generated in a CI tmpdir, so that gate stays red however fresh the vendored copy is.

@estebanzimanyi
estebanzimanyi merged commit d61f187 into MobilityDB:master Aug 28, 2026
1 check passed
@estebanzimanyi
estebanzimanyi deleted the fix/parity-oracle-identity-is-reproducible branch August 28, 2026 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant