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
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
If we dont want to change logging libraries, i guess just a quick audit of where we use what library, can be a good conclusion to this issue. Otherwise, this could hit 100s of files so... lets make sure we think it through.
This is not a cosmetic issue: TF builds can take a while cumulatively, and we run them 100s of times a day, so how we log the timing of steps is important.
....
Bug description
Recently we got some non-machine readable logs while optimizing framework:
�$ /usr/local/go/bin/go mod download
and along the way, we realized we had a old, largely unmaintained library for our logging: github.com/aunum/log.
We have a PR to make those logs more readable #4183 w/o requiring emojis, but... the question of: what logging librarys we should use, where, for all of the framework components needs to be resolved...
... OTHERWISE one of these bad things can happen ...
new colored or emoji logs might pop up in places where we dont want them (backend build systems)....
or the opposite: we might use klog in user facing environments...
If we dont want to change logging libraries, i guess just a quick audit of where we use what library, can be a good conclusion to this issue. Otherwise, this could hit 100s of files so... lets make sure we think it through.
This is not a cosmetic issue: TF builds can take a while cumulatively, and we run them 100s of times a day, so how we log the timing of steps is important.
....
Bug description
Recently we got some non-machine readable logs while optimizing framework:
and along the way, we realized we had a old, largely unmaintained library for our logging:
github.com/aunum/log
.We have a PR to make those logs more readable #4183 w/o requiring emojis, but... the question of: what logging librarys we should use, where, for all of the framework components needs to be resolved...
... OTHERWISE one of these bad things can happen ...
Solution
tanzu cluster create
)make cli
)Affected product area (please put an X in all that apply)
Expected behavior
Steps to reproduce the bug
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)
The text was updated successfully, but these errors were encountered: