Actions
Bug #899
closedfindscu does not properly set exit codes
Start date:
2019-09-26
Due date:
% Done:
100%
Estimated time:
Module:
dcmnet
Operating System:
Compiler:
Description
In case of a network error such as...
E: Association Request Failed: 0006:031b Failed to establish association E: 0006:0317 Peer aborted Association (or never connected) E: 0006:031c TCP Initialization Error: Connection refused
... findscu returns with exit code 0, which is certainly not what a user expects (e.g. when starting findscu from a script).
The reason for this (wrong) exit code is that the "cond" variable is not evaluated after calling "cond = findscu.performQuery(...);". Also the return value of dropNetwork() and other methods is not checked to set the exit code.
Updated by Jörg Riesmeier almost 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Issue fixed with commit 883ede9.
Actions