feat: simd runs in-process testnet by default#9246
Conversation
|
I'd like some preliminary feedback on this draft PR, to get validation that others are aligned with this approach, and then i'd proceed with the following updates to clean this up:
Also, looking for feedback on naming :) In a follow-up PR, we should figure out how to expose keys to users for manual testing if we run these testnets in CI (with Heroku Review Apps or similar). Making a full on faucet seems out of scope for this work. Two alternatives I can think of (neither are secure at all, but maybe that's not a concern):
|
amaury1093
left a comment
There was a problem hiding this comment.
Concept ACK.
I feel like this is the software developer's answer ("just code it") to a devops problem. A better solution might be some cloud orchestration config and deployment. But maybe this PR is fine for now, since the maintainers of the SDK are mainly software devs, and this setup is something we know how to debug easily 👍
|
This is just CLI breaking for tests, thus doesn't merit a |
|
Also I think it's |
| * The `RegisterCustomTypeURL` function and the `cosmos.base.v1beta1.ServiceMsg` interface have been removed from the interface registry. | ||
| * (codec) [\#9251](https://github.com/cosmos/cosmos-sdk/pull/9251) Rename `clientCtx.JSONMarshaler` to `clientCtx.JSONCodec` as per #9226. | ||
| * (x/bank) [\#9271](https://github.com/cosmos/cosmos-sdk/pull/9271) SendEnabledCoin(s) renamed to IsSendEnabledCoin(s) to better reflect its functionality. | ||
| * [\#9246](https://github.com/cosmos/cosmos-sdk/pull/9246) The `New` method for the network package now returns an error. |
There was a problem hiding this comment.
cc @aaronc should this be an API breaking change?
I agree. Maybe simapp readme could be expanded upon or we could add another document to Running a Node. It looks like the #9014 might be relevant here. I've assigned myself to the issue. I'll work on adding some documentation. |
amaury1093
left a comment
There was a problem hiding this comment.
tACK, thanks @ryanchristo
my test:
./build/simd testnet start --v 10
./build/simd q staking validators // make sure there's 10 validators
I believe we actually want the |
amaury1093
left a comment
There was a problem hiding this comment.
Oh wait, no, I forgot about #9246 (comment). let's wait
|
@clevinson or @ryanchristo can one of you fix the changelog conflicts? |
amaury1093
left a comment
There was a problem hiding this comment.
tACK: ./build/simd testnet start
<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺ v ✰ Thanks for creating a PR! ✰ v Before smashing the submit button please review the checkboxes. v If a checkbox is n/a - please still include it but + a little note why ☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --> ## Description <!-- Add a description of the changes that this PR introduces and the files that are the most critical to review. --> This pull request is a follow-up pull request for #9246 that adds documentation for the `simd testnet` command. --- Before we can merge this PR, please make sure that all the following items have been checked off. If any of the checklist items are not applicable, please leave them but write a little note why. - [x] Targeted PR against correct branch (see [CONTRIBUTING.md](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#pr-targeting)) - [x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work. - [ ] Code follows the [module structure standards](https://github.com/cosmos/cosmos-sdk/blob/master/docs/building-modules/structure.md). - [ ] Wrote unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#testing) - [x] Updated relevant documentation (`docs/`) or specification (`x/<module>/spec/`) - [ ] Added relevant `godoc` [comments](https://blog.golang.org/godoc-documenting-go-code). - [ ] Added a relevant changelog entry to the `Unreleased` section in `CHANGELOG.md` - [x] Re-reviewed `Files changed` in the Github PR explorer - [x] Review `Codecov Report` in the comment section below once CI passes
<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺ v ✰ Thanks for creating a PR! ✰ v Before smashing the submit button please review the checkboxes. v If a checkbox is n/a - please still include it but + a little note why ☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --> ## Description ref: cosmos#9183 After some more recent conversations w/ @aaronc, I decided to go back to his original proposal of setting up a subcommand for running in-process testnets. This PR splits the `simd testnet` command into two subcommands: - `simd testnet start` which starts an in-process n-node testnet - `simd testnet init-files` which sets up configuration & genesis files for an n-node testnet to be run as separate processes (one per node, most likely via Docker Compose) --- Before we can merge this PR, please make sure that all the following items have been checked off. If any of the checklist items are not applicable, please leave them but write a little note why. - [x] Targeted PR against correct branch (see [CONTRIBUTING.md](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#pr-targeting)) - [x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work. - [x] Code follows the [module structure standards](https://github.com/cosmos/cosmos-sdk/blob/master/docs/building-modules/structure.md). - **n/a** - [ ] Wrote unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#testing) - [x] Updated relevant documentation (`docs/`) or specification (`x/<module>/spec/`) - **see cosmos#9411** - [x] Added relevant `godoc` [comments](https://blog.golang.org/godoc-documenting-go-code). - [x] Added a relevant changelog entry to the `Unreleased` section in `CHANGELOG.md` - [x] Re-reviewed `Files changed` in the Github PR explorer - [ ] Review `Codecov Report` in the comment section below once CI passes
Description
ref: #9183
After some more recent conversations w/ @aaronc, I decided to go back to his original proposal of setting up a subcommand for running in-process testnets.
This PR splits the
simd testnetcommand into two subcommands:simd testnet startwhich starts an in-process n-node testnetsimd testnet init-fileswhich sets up configuration & genesis files for an n-node testnet to be run as separate processes (one per node, most likely via Docker Compose)Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/) or specification (x/<module>/spec/) - see docs: simd testnet commands #9411godoccomments.Unreleasedsection inCHANGELOG.mdFiles changedin the Github PR explorerCodecov Reportin the comment section below once CI passes