chore: Sync upstream and preserve routing extensions - #8
Merged
Merged
Conversation
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
4 participants
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.
Bring the Lugg fork current with upstream through
ea3c4ddwhile retaining the routing extensions used by the dispatch planner. This adds upstream routing breaks, slack costs, constraint support, and parameter bindings.The merge keeps native solution tracing, improvement limits, piecewise cumul costs, callback-aware GVL release for model closing and restoration, and fractional restoration time limits. In
RoutingModel, restoration still converts routes into owned C++ values before releasing the GVL and returns a non-owning assignment wrapper afterward. The overlapping upstream wrapper is reconciled into that implementation; both piecewise costs and upstream break support remain available.The full native suite passes locally, including all fork-specific regressions. A direct solve also exercises the newly merged break and slack-cost bindings. Merge this PR with a merge commit so upstream ancestry remains intact; do not squash or rebase it. The API dependency pin changes separately in https://github.com/lugg/api/pull/4007.