-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardise logging, error message formatting,wrapping etc across codebase #2371
Comments
@Rakshith-R Yes true, there are lots of un-uniformity across the codebase regarding logging, error messages, etc. It will be good to document a fixed format and have small patches to fix it. |
Yes, standardization on logging format would be nice. I prefer the format like |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
@Yuggupta27 considering we havent made progress here, I am removing this from release 3.6 tracker and tracking for release 3.7. |
@Yuggupta27 considering we havent made progress here, I am removing this from release 3.7 tracker and tracking for release 3.8. |
Sure, I am currently caught up with other things so un-assigning myself from this issue for the time being. |
Describe the feature you'd like to have
Standardised logging, error message formatting,wrapping etc across code base.
Currently, we use a variety of logging (Info,Debug,Error) and error formatting (
"failed with ... with err %w"
,"failed with ... : %w"
).Its good to document these and keep it uniform across codebase.
How will we know we have a good solution? (acceptance criteria)
Add a list of criteria that should be met for this feature to be useful
Please comment your suggestions below.
cc @nixpanic @yati1998
The text was updated successfully, but these errors were encountered: