The publish_qc command doesn't correctly handle non-standard QC protocols: the protocol name is extracted from the qc.info file for the QC directory and passed directly to the report_qc.py utility, but if this is not one of the built-in protocols then the utility immediately stops with exit code 1 (indicating that the QC has not been verified).
A better way to handle this would be to allow report_qc.py to use the QC protocol specification for verification directly from the stored metadata (which is the default), with the protocol name used as a fallback if no specification is stored.
(This bug manifests itself for example when attempting to publish QC reports for projects that have used custom protocols which are not in the list of built-in protocols.)
The
publish_qccommand doesn't correctly handle non-standard QC protocols: the protocol name is extracted from theqc.infofile for the QC directory and passed directly to thereport_qc.pyutility, but if this is not one of the built-in protocols then the utility immediately stops with exit code 1 (indicating that the QC has not been verified).A better way to handle this would be to allow
report_qc.pyto use the QC protocol specification for verification directly from the stored metadata (which is the default), with the protocol name used as a fallback if no specification is stored.(This bug manifests itself for example when attempting to publish QC reports for projects that have used custom protocols which are not in the list of built-in protocols.)