Skip to content
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

Clean up some noisy logging #2459

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Clean up some noisy logging #2459

merged 1 commit into from
Jan 16, 2025

Conversation

jbearer
Copy link
Member

@jbearer jbearer commented Jan 16, 2025

Don't log warning when a requested object is simply not found; it is considered normal for nodes to sometimes be missing this data. We should only warn when there is some other error when looking up the data (connection closed ,etc)

@jbearer jbearer merged commit 9e69a39 into main Jan 16, 2025
22 checks passed
@jbearer jbearer deleted the jb/logging branch January 16, 2025 17:34
Copy link
Contributor

Successfully created backport PR for release-labrador:

github-actions bot pushed a commit that referenced this pull request Jan 16, 2025
Don't log warning when a requested object is simply not found

(cherry picked from commit 9e69a39)
jbearer added a commit that referenced this pull request Jan 16, 2025
Clean up some noisy logging (#2459)

Don't log warning when a requested object is simply not found

(cherry picked from commit 9e69a39)

Co-authored-by: Jeb Bearer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants