Duke-GCB / Duke-GCB/DukeDSClient
Progress bar not visible in k8s logs
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
When DukeDSClient is run inside a k8s container the progress bar isn't visible.
This is due to how logging works within k8s - It holds the output until a newline is printed.
The current progress bar rewrites the same line without adding a newlines as it progresses.
This means there will be no output until the upload or download operation is complete when running inside k8s.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.