Closed david-waterworth closed 9 months ago
Sorry, this can't be changed as it is a breaking change. See Disabling-logs in the docs to modify the log level for gql.
bumping this issue. I see you've marked as duplicate, but is this being adressed?
@olivierpilotte it doesn't appear so, I don't understand why it cannot be changed but the maintainers consider fixing this a breaking change and closed my issue. You have to manually set the logging level per transport as per the doc link above, i.e.
from gql.transport.requests import log as requests_logger
requests_logger.setLevel(logging.WARNING)
@david-waterworth I'm running a query from Airflow, and for some reason, disabling the logs this way does not work. Not fixed in 3.6.0b0
nor 3.6.0b1
@leszekhanusz can we have a quick follow-up on this issue? Is there a plan for a permanent fix?
@olivierpilotte yes I'm seeing something similar when I enable logging in a notebook running in vscode - even though I've disabled the transport log it still generates log messages.
Common problems
My applications log is filled with the payload of every request/response. For example
Note this is at log level INFO, specifically https://github.com/graphql-python/gql/blob/48bb94cc4fc0755419c9edc7e8ef1470036c193d/gql/transport/requests.py#L234-L235
Describe the bug Debug messages should not be logged at INFO level
To Reproduce Set log level to INFO
Expected behavior If required this should be logged at DEBUG lebel
System info (please complete the following information):