Fix bug in XpressPersistent.update_var#3566
Merged
jsiirola merged 2 commits intoPyomo:mainfrom Apr 16, 2025
Merged
Conversation
michaelbynum
approved these changes
Apr 15, 2025
jsiirola
approved these changes
Apr 15, 2025
Member
jsiirola
left a comment
jsiirola
left a comment
There was a problem hiding this comment.
Looks good, pending successful tests.
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.
Fixes #3565
Summary/Motivation:
XpressPersistent.update_varwas not behaving as I expected (see #3565)Changes proposed in this PR:
XpressPersistent.update_varto change the variable type first, and then change the boundsLegal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: