-
Notifications
You must be signed in to change notification settings - Fork 25
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
Option to enable Verbose output to run tab + styled fallback when no socket #513
Merged
Merged
Changes from 10 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
62faf7b
Add additional arguments to the run command, needs OS 3.4.0. We shou…
macumber 76c67b1
Merge branch 'develop' into 110_workflow_stdout
macumber 9ccc0b7
Merge branch 'develop' into 110_workflow_stdout
jmarrec f764765
Merge branch 'develop' into 110_workflow_stdout
jmarrec db36d1f
Add a checkbox to enable --verbose cli option, do not use show-stdout…
jmarrec d71b389
Style stdout/stderr in OSApp when verbose=true
jmarrec 8181ad8
Write the verboseOutput to the settings for persistence (and read fro…
jmarrec 22a0a3d
Capture exit code when not zero and output it
jmarrec af2435a
Implement a fallback when socket can't be opened: still display and s…
jmarrec 175e8a0
Connect QProcess::errorOccurred to catch bad things happening like E+…
jmarrec dd97abe
Output the stdout/stderr to a companion_dir/ in addition of displayin…
jmarrec 0511cf7
Move the touch where it should be
jmarrec 2d5a1f2
Apparently this was seen as a variable declaration, so use brace init
jmarrec 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 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 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 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.
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.
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.
Will E+ stdout and stderr still be in files in the sim dir for the user to read later? I see stdout-energyplus and stderr-energyplus files but I'm not entirely sure which process was writing those, the app or the cli.
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.
stdout-energyplus stderr-energyplus are written by workflow gem.
What I am no longer outputing is the model_companion_dir/stdout and stderr files. I see no value in keeping those, when we are seeing them live. I don't see any use case for seeing them afterwards, but perhaps there is one. In which case the RunView::readyReadStandardOutput and RunView::readyReadStandardError should be writting to these files in append mode in addition of displaying them live. thoughts @macumber ?
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.
Ok yeah, I don't think those two files are useful. Thanks Julian!
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.
cf dd97abe