fix(node): handle missing corechannel aggregate and add --corechannel-address#133
Merged
Conversation
…-address Add error_for_status() to get_aggregate so non-2xx responses (e.g. 404 on a fresh devnet) produce a clear HTTP error instead of a confusing serde parse failure. Add --corechannel-address option to `node list` so consumers can point at a different aggregate owner than the hardcoded mainnet address.
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
1 participant
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.
Add error_for_status() to get_aggregate so non-2xx responses (e.g. 404 on a fresh devnet) produce a clear HTTP error instead of a confusing serde parse failure.
Add --corechannel-address option to
node listso consumers can point at a different aggregate owner than the hardcoded mainnet address.