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 would be nice to be able to disable the progress bars you see with lakectl local clone and other bulk operations.
Use case: I have some ML training jobs that run in a Kubernetes cluster. That cluster has logging set up so anything a container logs gets sent to an external logging service. Those services typically expect logs to be in a pretty simple format like 1 line per thing logged or in JSON format. However, the progress bars use special characters (e.g. \r) to update the cool little graphs and that confuses the heck out of the log parsers. It's still nice to have logs like downloaded some/file.txt but the progress bars are problematic. Ideally you'd detect that the lakectl stdout isn't a terminal and if that's the case convert the progress bar logs to "regular logs". If that's not possible a flag like --disable-progress would be great.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to disable the progress bars you see with
lakectl local clone
and other bulk operations.Use case: I have some ML training jobs that run in a Kubernetes cluster. That cluster has logging set up so anything a container logs gets sent to an external logging service. Those services typically expect logs to be in a pretty simple format like 1 line per thing logged or in JSON format. However, the progress bars use special characters (e.g.
\r
) to update the cool little graphs and that confuses the heck out of the log parsers. It's still nice to have logs likedownloaded some/file.txt
but the progress bars are problematic. Ideally you'd detect that thelakectl
stdout isn't a terminal and if that's the case convert the progress bar logs to "regular logs". If that's not possible a flag like--disable-progress
would be great.The text was updated successfully, but these errors were encountered: