Repository navigation
Fix bug #2042 absence of logs on mPDLP error with C API and not using rhs when present #2091
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+267
−228
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: NVIDIA/cuopt
Length of output: 29145
🏁 Script executed:
Repository: NVIDIA/cuopt
Length of output: 40300
🏁 Script executed:
Repository: NVIDIA/cuopt
Length of output: 41711
Validate
expand_rhsinputs and document the public helper.The MPS parser and documented
cuOptCreateProbleminputs provide matching RHS and row-type arrays. However, the public model setters do not enforce that invariant, andcuOptCreateProblemcopies arbitrary constraint-sense characters without validating them.expand_rhscan therefore read pastconstraint_boundsor silently omit an unsupported row type. The shortened bounds can fail dimension checks or map later bounds to the wrong matrix rows. Add the size check and reject unsupported row types.The empty-
row_typescase is not established for the MPS parser orcuOptCreateProblem; both populate row types for each constraint. Do not use that case as the primary justification.Add Doxygen documentation because
expand_rhsis a new function in a public header.Suggested validation fix
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is just code that was shifted from the presolve part. I dont want to add new features in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BubullzzUnderstood. Thanks for clarifying. The validation gap comes from the existing presolve code, not from this extraction. I agree that adding validation can stay outside this PR.The existing repository guidance also identifies these C++ headers as internal. My public-API documentation request was incorrect.
Would you like me to open a follow-up issue for the validation gap?
✏️ Learnings added
🧠 Learnings used
You are interacting with an AI system.