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
Currently, all process outputs is automatically published to the given output directory.
It is a behaviour that is interesting for debugging, but in production, it slow downs the job and consumes space for nothing as we are not interested in keeping all intermediate outputs.
One possibility to fix this is to keep the publish logic in place but activate it only when a specific boolean parameter is passed (ex: --debug or --publish-intermediate-outputs ).
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Currently, all process outputs is automatically published to the given output directory.
It is a behaviour that is interesting for debugging, but in production, it slow downs the job and consumes space for nothing as we are not interested in keeping all intermediate outputs.
One possibility to fix this is to keep the publish logic in place but activate it only when a specific boolean parameter is passed (ex: --debug or --publish-intermediate-outputs ).
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: