-
Notifications
You must be signed in to change notification settings - Fork 14
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
chore: update testnet channels again #124
Conversation
@@ -259,7 +259,8 @@ fn process_chain_config(chain_config: ChainConfig) -> AppResult<Registry> { | |||
.join("assetlist.json"); | |||
|
|||
// Parse the local JSON into the AssetList struct | |||
let data = fs::read_to_string(assetlist_path)?; | |||
let data = fs::read_to_string(assetlist_path.clone()).context( | |||
"failed to read cosmos asset info; did you remember to clone the repo with submodules enabled?")?; |
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.
may this save a future maintainer 10m of hair-pulling 🖖
This channel was opened this morning by @erwanor, to test the latest code changes just deployed to the Noble testnet. Refs penumbra-zone/penumbra#4899
a5f5749
to
70a6090
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.
we should be able to just manually run pnpm changeset publish
after merge to publish v12.2.0
which consumes these changes (think the changeset bot hasn't been detecting changesets because it's in npm/
rather than root)
Fairly straightforward change: bump the osmo testnet channel.
Testing and review
I'd like to verify that this setting works, in a local build of prax, but have been unable to do so. Documented some suggestions in #80 (comment).