Skip to content

fix: Replace some workflows exception logging with warning and include context #4590

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

Conversation

VladimirFilonov
Copy link
Contributor

Updated the exception handling across various modules to use logger.warning instead of logger.exception or logger.error, providing better context with exc_info and additional metadata. This improves the clarity and debugging capabilities of the logged errors without being overly verbose.

Closes #4589

📑 Description

✅ Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

ℹ Additional Information

…text

Updated the exception handling across various modules to use `logger.warning` instead of `logger.exception` or `logger.error`, providing better context with `exc_info` and additional metadata. This improves the clarity and debugging capabilities of the logged errors without being overly verbose.
Copy link

vercel bot commented Apr 18, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
keep ⬜️ Ignored (Inspect) Visit Preview Apr 21, 2025 5:05am

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Apr 18, 2025
The exception variable `ex` was unused and has been removed to clean up the code. This change simplifies the exception handling while maintaining the current behavior.
@shahargl
Copy link
Member

@VladimirFilonov is there any example of the differences? as far as I know logger.exception logs the stack trace

@VladimirFilonov
Copy link
Contributor Author

@shahargl yes, but with Error level, which creates a lot of noise in logs filtered by ERROR

Copy link
Contributor

@skynetigor skynetigor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@VladimirFilonov VladimirFilonov merged commit da16fb3 into main Apr 22, 2025
18 checks passed
@VladimirFilonov VladimirFilonov deleted the fix/4589-bug-misconfigured-workflows-generates-a-lot-of-errors-in-logs-which-is-noisy branch April 22, 2025 07:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[🐛 Bug]: Misconfigured workflows generates a lot of errors in logs, which is noisy
3 participants