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
When running argo logs -f on any workflow that runs for long enough, the logs are sprinkled with lines that start like this:
INFO[0068] Re-establishing workflow watch
(The namespace and workflow name are also listed after several spaces.) These logs are usually only present when invoking a higher --loglevel, like debug (this is using the default, info). This appears to be a mistaken byproduct of a fix to #2796.
What you expected to happen:
Those logs should be on the debug level, not the info level.
How to reproduce it (as minimally and precisely as possible):
Run the workflow in #2796 and then run argo logs -f on the result. A line like the above will appear after a bit over a minute.
This is in Argo v2.7.6, which has the fix to #2796.
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Checklist:
What happened:
When running
argo logs -f
on any workflow that runs for long enough, the logs are sprinkled with lines that start like this:(The namespace and workflow name are also listed after several spaces.) These logs are usually only present when invoking a higher
--loglevel
, likedebug
(this is using the default,info
). This appears to be a mistaken byproduct of a fix to #2796.What you expected to happen:
Those logs should be on the debug level, not the info level.
How to reproduce it (as minimally and precisely as possible):
Run the workflow in #2796 and then run
argo logs -f
on the result. A line like the above will appear after a bit over a minute.This is in Argo v2.7.6, which has the fix to #2796.
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: