Conversation
makes 'unused variable' warnings in runner.py meaningful - this bit @AMINOexe when running into an 'algorithm is not supported' error despite having the class prepared.
This was referenced Jul 18, 2025
Open
90ee7a3
Collaborator
Author
Collaborator
|
Why was it automatically closed? All the commits from this branch also belonged to the branch of the merged PR? I don't recall seeing that behavior before. |
Collaborator
Author
They did: I designed this PR and split it up into the other PRs (e.g. in #329 you can find commits where I undo algorithm seeding.) |
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.
Do not review this. The actual changes this PR makes are hard to see. See the two PRs below.
Closes #323. Closes #174.