Skip to content

Re-classify unnecessary ldata logging as DEBUG #526

@skovaka

Description

@skovaka

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions