-
Notifications
You must be signed in to change notification settings - Fork 1
[Dependencies] Updating Credfeto.Docker.HealthCheck.Http.Client (Docker healthcheck http client) to 0.0.72.928 #383
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
Open
github-actions
wants to merge
6
commits into
main
Choose a base branch
from
depends/update-credfeto.docker.healthcheck.http.client/0.0.72.928
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8bc00a5
[Dependencies] Updating Credfeto.Docker.HealthCheck.Http.Client (Dock…
credfeto 18da340
fix: pass ILogger to HealthCheckClient.ExecuteAsync after API change …
dnyw4l3n13 0b612ce
chore: update changelog for ILogger fix in HealthCheckClient.ExecuteA…
dnyw4l3n13 487b25a
fix: use console logger for health check to surface HealthCheckFailed…
dnyw4l3n13 9d00ac2
chore: remove stale Credfeto.Docker.HealthCheck.Http.Client 0.0.61.65…
dnyw4l3n13 b6336a3
chore: remove superseded FunFair.Test.Common 6.2.17.1982 changelog entry
dnyw4l3n13 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Observability gap: non-2xx HTTP responses return exit code 1 with no log output
The console logger added here only surfaces diagnostics on the exception path. Decompiling
Credfeto.Docker.HealthCheck.Http.Client0.0.72.928 confirms the relevant code:There is no
ILoggercall on the non-2xx path — only on the caught-exception path (logger.HealthCheckFailed(uri, exception)). If the health endpoint returns 503, 500, or any non-2xx status, the process exits with code 1 and the console logger produces zero output. Docker marks the container unhealthy, but the operator sees nothing in the logs.This is a library limitation, not something introduced in this PR — but it means the stated goal of "surface HealthCheckFailed errors" is only partially achieved: exception failures are now visible, non-2xx failures remain silent.
Consider wrapping the call to add our own logging for the non-2xx case, or raise an issue against
credfeto/credfeto-docker-healthcheck-http-clientto add logging for non-success status codes.