Repository navigation
Conversation
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4808 +/- ##
==========================================
+ Coverage 67.61% 67.65% +0.04%
==========================================
Files 254 254
Lines 33609 33622 +13
==========================================
+ Hits 22725 22748 +23
+ Misses 10883 10873 -10
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
aly-obol
approved these changes
Oct 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



Sends a
User-Agent: charon/<version>header on every Obol API request, so the API can attribute traffic. Today every Go client shows up asGo-http-client/1.1. The newWithUserAgent(product)client option lets tools built on this package put themselves in front, e.g.lido-dv-exit/v0.7.0 charon/v1.12.0.httpPost,httpGetandhttpDeletebecomeClientmethods so they can read the header from the client.PostFeeRecipientsFetch, which builds its own request, sets it too.A 404 response to a POST now returns the new
ErrLockNotFoundsentinel, matched on status, not body text. The error keeps itsstatusandbodyfields. Before, 404s were a generichttp POST failederror, so callers couldn't tell "the cluster lock isn't published to this API" from a transient failure. lido-dv-exit retried such a cluster forever without telling the operator.PostFeeRecipientsFetch's existing "cluster is unknown to the API" error now wraps it too.httpGetalso closes the response body on non-2xx responses; the 404 path used to leak it.category: feature
ticket: none