You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the diagnose utility prints all output to stdout and returns 0 regardless of warnings. Would it make sense to return a non-zero exit status if there's an error with any of the checks?
This would make it easier to programmatically distinguish CmdStan runs with diagnostic warnings in the shell. As far as I know, currently the diagnose output needs to be checked manually or the output loaded into one of the programming language specific packages.
The return line in diagnose.cpp can just return the bool value from the variable has_error, or a more specific exit code can be used.
The text was updated successfully, but these errors were encountered:
the diagnose command detects potential errors - it returns warnings.
however, your point is valid - the return code could be used to signal warnings / no_warnings.
Currently, the
diagnose
utility prints all output to stdout and returns 0 regardless of warnings. Would it make sense to return a non-zero exit status if there's an error with any of the checks?This would make it easier to programmatically distinguish CmdStan runs with diagnostic warnings in the shell. As far as I know, currently the
diagnose
output needs to be checked manually or the output loaded into one of the programming language specific packages.The return line in diagnose.cpp can just return the bool value from the variable
has_error
, or a more specific exit code can be used.The text was updated successfully, but these errors were encountered: