You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For point 1, technically speaking I think both these message should use logging.debug (not info) rather than click.echo. Since by default these messages should not show to a user (confirmed by @yetudada in sprint planning) then setting them to use logging.debug will make them disappear.
So all that should be needed here is modifying L64 and L57 to both use logging.debug, check that the messages disappear when you do kedro run, and update any tests affected.
Note, as per discussion in kedro-org/kedro#1546, at the moment there's no way for a user to change whether or not the kedro-telemetry messages are shown by altering project-side logging.yml because before_command_run hooks are run before that logging configuration is set up. This is fine for now.
The text was updated successfully, but these errors were encountered:
There's two problems with how kedro-telemetry does logging at the moment:
click.secho
and sometimes it uses logging. This is inconsistent.For point 1, technically speaking I think both these message should use
logging.debug
(not info) rather thanclick.echo
. Since by default these messages should not show to a user (confirmed by @yetudada in sprint planning) then setting them to uselogging.debug
will make them disappear.So all that should be needed here is modifying L64 and L57 to both use
logging.debug
, check that the messages disappear when you dokedro run
, and update any tests affected.Note, as per discussion in kedro-org/kedro#1546, at the moment there's no way for a user to change whether or not the kedro-telemetry messages are shown by altering project-side logging.yml because
before_command_run
hooks are run before that logging configuration is set up. This is fine for now.The text was updated successfully, but these errors were encountered: