Repository navigation
fix(runtime): target SolverForge 0.26.1 - #9
Merged
Merged
Conversation
The README now says the app preserves the scheduling concepts of the original Java application.
SolverForge 0.26.1 keeps late acceptance's score history unless a hard or medium level changes, so the five apps that search with late acceptance accept the worsening moves the algorithm is meant to accept again, and its scalar ruin/recreate draws batches without an entity-sized permutation. Every app requests and locks the 0.26.1 crates, and its app metadata, README and WIREFRAME name the new runtime target. Closes #8
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.
Closes #8. Gates on this tree against published 0.26.1: make ci-local EXIT 0 (294 passed, 0 failed); make pre-release EXIT 0 for all eight apps.