potiuk commented on issue #31655: URL: https://github.com/apache/airflow/issues/31655#issuecomment-1593602707
And **just** to explain what's going on (and I hope you read my message above) - the message is printed while airflow is importing stuff. This is happening **before** airflow knows what command is executed. Therefore if anything prints anything during that import, the command to run has no chance to disable logging, because by the time we know which command we run the output is well, already printed. There might be hacks to somehow mitigate it. you could probably have a list of possible arguments passed to the CLI to determine that you should suppress INFO logging. That would be super-hacky way of solving the problem. BUT this would be super difficult to maintain, and generally speaking printing ANYTHING to the log at INFO while importing the code is inherently incompatible with any CLI application that wants to print something at the output that is parseable. If you print anything in the log while importing, then the problem is for example that you have no chance whatsoever to change the logging level of your application - because you should do it generally after everything you need is imported not before or duing the import. The plugin you use has a bug and should be fixed. The way to handle it is to disable or remove the plugin so that it won't pollute the output with log that it should not be doing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
