This repository has been archived by the owner on Dec 7, 2021. It is now read-only.
Fix NLOpt optimizers trying to iterate NoneType #1414
Merged
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.
Bounds were assumed to be a an array of tuples. No bound being (None, None) tuple for each param. Passing None as the bounds array (default when not explicitly set) always iterated through bounds to set thing up and failed trying to iterate NoneType. This was reported in external Slack workspace https://qiskit.slack.com/archives/C7SJ0PJ5A/p1602918563027800 (if you cannot access the link and want to there is a link here to join the community https://github.com/Qiskit/qiskit-aqua#contribution-guidelines ). Here is a summary though