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
It appears as though that aegean within the singularity container outputs it logs to the stderr. In the current form I am not currently capturing the stderr in the prefect logs. It seems that the actual subprocess call is managed within spython (the python module that constructs singularity commands) does not output the stderr to the logger object I am looping over in flint.sclient.run_singularity_command.
I am not sure whether we can easily hijack this output object ourselves, or whether an upstream pr should be considered.
The text was updated successfully, but these errors were encountered:
It appears as though that aegean within the singularity container outputs it logs to the stderr. In the current form I am not currently capturing the stderr in the prefect logs. It seems that the actual subprocess call is managed within spython (the python module that constructs singularity commands) does not output the stderr to the logger object I am looping over in
flint.sclient.run_singularity_command
.I am not sure whether we can easily hijack this output object ourselves, or whether an upstream pr should be considered.
The text was updated successfully, but these errors were encountered: