When using the python logging module, operations like downloading remote files or LPath.iterdir() generates a bunch of logging.INFO messages containing long dictionaries like this:
2025-02-24 16:40:42 - INFO - >>> {"query": "query LDataChildren($argPath: String!) {\n ldataResolvePathData(argPath: $argPath) {\n finalLinkTarget {\n type\n childLdataTreeEdges(filter: {child: {removed: {equalTo: false}}}) {\n nodes {\n child {\n name\n }\n }\n }\n }\n }\n}", "variables": {"argPath": "..."}}
2025-02-24 16:40:42 - INFO - <<< {"data":{"ldataResolvePathData":{"finalLinkTarget":{"type":"DIR","childLdataTreeEdges":{"nodes":[{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}},{"child":{"name":"..."}}]}}}}}
Performing many filesystem operations really fills up the workflow log and makes it hard to read. It seems like the level of these messages should be set to logging.DEBUG instead of logging.INFO? Thanks!
When using the python logging module, operations like downloading remote files or
LPath.iterdir()generates a bunch oflogging.INFOmessages containing long dictionaries like this:Performing many filesystem operations really fills up the workflow log and makes it hard to read. It seems like the level of these messages should be set to
logging.DEBUGinstead oflogging.INFO? Thanks!