Advance the MEOS commit and regenerate the UDF surface - #421
Closed
estebanzimanyi wants to merge 1 commit into
Closed
estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
estebanzimanyi
force-pushed
the
tooling/refresh-generated-surface
branch
from
September 30, 2026 06:47
2379d9f to
035f45a
Compare
Member
Author
|
Its commit, the MEOS pin advance and the regenerated surface, is in main together with the adaptation of src/geo/tgeompoint.cpp that the new pin requires: all ten files this branch changes are identical on main. |
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 committed
src/generated/drifted from a fresh derivation againstMobilityDB/MobilityDB master; this regenerates it and moves
_MEOS_REFinvcpkg_ports/meos/portfile.cmaketo the commit it isderived from, so libmeos and the surface stay one commit.
Opened by the
Refresh generated surface from MobilityDB masterworkflow.