Hi all, I am experiencing several log corruption i...
# questions
s
Hi all, I am experiencing several log corruption in GitLab CI where kedro logs are truncated, garbled, and sentences are cut off randomly, making them completely unreadable. I've already tried : PYTHONUNBUFFERED=1 PYTHONIOENCODING=utf-8 Has someone ever encountered this specific truncation/garbling issue in GitLab? Is this the known Rich library terminal detection issue in CI? Is there any kedro Specific solution to this problem?
d
hey, it's likely because of Rich logging, you can find here how to disable it https://docs.kedro.org/en/1.0.0/develop/logging/#how-to-use-plain-console-logging
s
Hey, Thank you for the pointer to the doc! I tried implementing the approach from the doc but still experiencing the same truncated/garbled output in gitlab CI. What all I implemented- 1. Created conf/base/loggin.yml with plain console handler 2. Set the environment variables in .xyz-project.yml Still seeing - Truncated logs in Gitlab CI output. QUESTION - 1. Is there a way to verify that kedro is actually using my custom logging.yml and not the default rich console? 2. Are there any other kedro internals that might still be using Rich console even with custom logging config? Any additional debugging steps would be appreciated!