fix timeout handling - #463
Merged
Merged
Conversation
* this was missing; default timout of 10.0s was always used
* use format as 'x.xx' * use unit 's' * add timeout information if model execution fails
Contributor
Author
adeas31
approved these changes
May 5, 2026
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
2 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.
the define timeout value (in OMCSession) is not propagated correctly to
ModelExecutionCmd()- thus, any change does not have the desired effectThis PR additionally improves the log / error messages to also provide the value of the (OMPython) timeout.
One function (
set_timeout()) was moved from OMCSessionABC to OMSessionABCReported in issue #460