-
Notifications
You must be signed in to change notification settings - Fork 210
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
fix: recognise vetted gateways configured in base meta #4138
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #4138 +/- ##
==========================================
- Coverage 58.29% 58.04% -0.25%
==========================================
Files 192 197 +5
Lines 42708 43722 +1014
==========================================
+ Hits 24896 25379 +483
- Misses 17812 18343 +531 ☔ View full report in Codecov by Sentry. |
7cd7c87
to
501d7b8
Compare
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.
Looks ok, one nit
- fedimint clients would only recognise [vetted gateways meta] field if configured via meta override url. This change allows clients to also read the same meta field on the base meta config
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin releases/v0.2
git worktree add -d .worktree/backport-4138-to-releases/v0.2 origin/releases/v0.2
cd .worktree/backport-4138-to-releases/v0.2
git switch --create backport-4138-to-releases/v0.2
git cherry-pick -x 13a54346c3ebb5d63df4f735316a4be70b0afc64 |
Fedimint clients would only recognise [vetted gateways meta] field if configured via meta override url. This change allows clients to also read the same meta field on the base meta config. vetted gateways meta value from
meta_override_url
is preferred over value supplied from the base meta.