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
tx client exits with exit code 0 when it shouldn't. An exit code of 0 (zero) means on linux the program has done its tasks without error.
Despite of this, tx client returns 0 even if it failed to finish its task properly.
Expected behaviour:
tx client mustn't return 0 (zero) in case of the requested task wasn't done.
In case the command can't finish its task for some reason, it is expected to
return at least a value of 1 (one), or a separate number other than zero for each type of error.
Example:
$ tx pull -s
# Getting info about resources
test-project.test-files - Resource test-project.test-files does not exist
[##############################] (1 / 1)
$ echo $?
0
The text was updated successfully, but these errors were encountered:
Additional information:
On some other error conditions tx client returns 1 (one) properly.
Re-checking the error described in #173, this time I counterchecked with echo $? after execution, and this command came properly back with 1 after the transmission of one of the files failed. So obviously only some of the tx commands are subject of not returning proper exit status after execution of the task failed.
Scope:
Focus:
Issue:
Despite of this, tx client returns 0 even if it failed to finish its task properly.
Expected behaviour:
In case the command can't finish its task for some reason, it is expected to
return at least a value of 1 (one), or a separate number other than zero for each type of error.
Example:
The text was updated successfully, but these errors were encountered: