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
In general, CLIs are not expected to produce logging output: they take in stdin and command line args, and output stdout and stderr. Our CLI does have at least one exception: we start a server with start dev. However, warnings and errors from short "transactional" commands should just be printed to stderr as plain natural language, without timestamps or other metadata.
One example of a current violation is
$ temporal operator namespace create default
time=2024-05-17T17:42:01.766 level=WARN msg="Passing the namespace as an argument is now deprecated; please switch to using -n instead"
The text was updated successfully, but these errors were encountered:
Other examples of incorrect logging behavior include:
Here, an invalid update request was made. The CLI should print the error message without formatting it as a log message.
$ /opt/homebrew/bin/temporal workflow update --workflow-id doesnotexist --name update1
time=2024-08-27T09:47:51.644 level=ERROR msg="unable to update workflow: sql: no rows in result set"
Here, ctrl-c on a CLI should just exit with non-zero shell process exit status. It’s not normal for a CLI to produce an ERROR-level log message on ctrl-c
In general, CLIs are not expected to produce logging output: they take in stdin and command line args, and output stdout and stderr. Our CLI does have at least one exception: we start a server with
start dev
. However, warnings and errors from short "transactional" commands should just be printed to stderr as plain natural language, without timestamps or other metadata.One example of a current violation is
The text was updated successfully, but these errors were encountered: