noisy warning: Flag "[name]" accessed without a request, which is likely in the context of a celery task.

[DanielVZ96]

This warning is appearing 29 times during provisioning in the edx-platform repo. It clutters logs and hinders dev experience (openedx/edx-platform#32888).

@regisb does this still need to be a warning? I'm trying to figure if I should ignore it in the edx-platform logs, or even if it should be moved to info/debug here.

Specific line of the warning: https://github.com/openedx/edx-toggles/blob/b93431d/edx_toggles/toggles/internal/waffle/flag.py#L79-L83

[regisb]

@regisb does this still need to be a warning?

I think it should still be a warning, but it should be deactivated in the context of provisioning.

[DanielVZ96]

@regisb hmm, should we just disable all python warnings during provisioning? I think at this point any relevant warning is lost in the huge amount of logs.

cc: @Agrendalath

[regisb]

I don't think so, no. Python warnings are useful, when used correctly. They indicate deprecated packages, soon-to-be-changing APIs, etc. In general, warnings should be resolved, not muted.

In the case at hand, if it is correct behaviour to access a particular flag without a request, then the logging level should be lowered to something like INFO.