v0.34.x: Rename Tendermint to CometBFT in /docs (backport #197)#251
v0.34.x: Rename Tendermint to CometBFT in /docs (backport #197)#251
Conversation
* docs/rename: simple github.com links renaming * docs/rename: old links to spec repo replaced * docs/rename: Go doc links renamed, currently broken * docs/rename: fixing broken links, proper branches * docs/rename: docs.tendermint.com -> docs.cometbft.com * docs/rename: fixing front matter in .md files * docs/rename: renaming in what is tendermint page * Tendermint in a Nutshell image removed * docs/rename: cleaning, renaming docs introduction * docs/rename: renaming in docs/app-dev/ dir * docs/rename: links to main branch in docs/networks * docs/rename: renaming in docs/tools/ dir * docs/rename: renaming in docs/tutorials dir * docs/rename: moving images to docs/imgs/ dir * docs/rename: renaming in docs/tendermint-core/ dir * docs/rename: docs/tendermint-core/ -> docs/core/ * docs/rename: renaming in docs/qa/ sub path * docs/rename: renaming in .vuepress dir, logo removed * docs/rename: renaming in READMEs * docs/rename: removing Tendermint images and content * docs/rename: removing references to removed diagram * docs/rename: renaming in READMEs for RFCs and ADRs * rename: links to docs/tendermint-core -> docs/core * docs/rename: removing unused images from docs/imgs/ * docs/rename: cleaning of docs/imgs/, ADR images moved * Apply suggestions from code review Co-authored-by: Thane Thomson <connect@thanethomson.com> * Apply suggestions from code review Co-authored-by: Thane Thomson <connect@thanethomson.com> * docs/rename: removing outdated Testnets section Co-authored-by: Thane Thomson <connect@thanethomson.com> * docs/rename: removing reference to tendermint/awesome repo Co-authored-by: Thane Thomson <connect@thanethomson.com> * docs/rename: contributing section updated Co-authored-by: Thane Thomson <connect@thanethomson.com> --------- Co-authored-by: Thane Thomson <connect@thanethomson.com> (cherry picked from commit 9883814) # Conflicts: # docs/.vuepress/redirects # docs/DOCS_README.md # docs/README.md # docs/app-dev/abci-cli.md # docs/app-dev/app-architecture.md # docs/app-dev/getting-started.md # docs/app-dev/indexing-transactions.md # docs/architecture/README.md # docs/architecture/adr-047-handling-evidence-from-light-client.md # docs/architecture/adr-056-light-client-amnesia-attacks.md # docs/architecture/adr-059-evidence-composition-and-lifecycle.md # docs/architecture/adr-template.md # docs/core/block-structure.md # docs/core/block-sync.md # docs/core/fast-sync.md # docs/core/how-to-read-logs.md # docs/core/running-in-production.md # docs/core/subscription.md # docs/core/using-cometbft.md # docs/introduction/architecture.md # docs/introduction/what-is-cometbft.md # docs/qa/v037/README.md # docs/rfc/README.md # docs/tendermint-core/block-sync.md # docs/tendermint-core/rpc.md # docs/tools/debugging.md # docs/tutorials/go-built-in.md # docs/tutorials/go.md # spec/consensus/consensus.md # spec/consensus/wal.md
| Try some other transactions and queries to make sure everything is | ||
| working! | ||
|
|
||
| ## Counter - Another Example |
There was a problem hiding this comment.
This second example was removed from main. Should we maintain it in this branch?
| You could put the commands in a file and run | ||
| `abci-cli --verbose batch < myfile`. | ||
|
|
||
| ## Counter - Another Example |
There was a problem hiding this comment.
This second example was removed from main. Should we maintain it in this branch?
5d3588d to
fe0c7bb
Compare
| - `max_num`: This sets the maximum number of evidence that can be committed | ||
| in a single block. and should fall comfortably under the max block | ||
| bytes when we consider the size of each evidence. | ||
| - `max_bytes`: This sets the maximum size in bytes of evidence that can be committed |
There was a problem hiding this comment.
is this also renamed in the code?
There was a problem hiding this comment.
max_bytes is on ./proto/tendermint/types/params.pb.go, max_num is not.
| "max_age_num_blocks": "100000", | ||
| "max_age_duration": "172800000000000", | ||
| "max_num": 50, | ||
| "max_bytes": 51200, |
There was a problem hiding this comment.
Again, double check whether it is actually renamed in the code.
| _200 Node Test_, and _Rotating Nodes Test_. | ||
|
|
||
| [releases]: https://github.com/tendermint/tendermint/blob/v0.37.x/RELEASES.md#large-scale-testnets | ||
| [releases]: https://github.com/cometbft/cometbft/blob/main/RELEASES.md#large-scale-testnets |
There was a problem hiding this comment.
| [releases]: https://github.com/cometbft/cometbft/blob/main/RELEASES.md#large-scale-testnets | |
| [releases]: https://github.com/cometbft/cometbft/blob/v0.34.x/RELEASES.md#large-scale-testnets |
?
There was a problem hiding this comment.
The file doesn't exist in branch v0.34.x...
|
|
||
| key, value := parts[0], parts[1] | ||
|
|
||
| // check if the same key=value already exists |
There was a problem hiding this comment.
Is this removed in the code too?
There was a problem hiding this comment.
The new version of the tutorial doesn't include this more comprehensive check...
But which code are you referring to?
There was a problem hiding this comment.
Sorry, I thought this was actually written as some example somewhere in the code as well. My bad.
Co-authored-by: Jasmina Malicevic <jasmina.dustinac@gmail.com>
| For the underlying key-value store we'll use | ||
| [badger](https://github.com/dgraph-io/badger), which is an embeddable, | ||
| persistent and fast key-value (KV) database. | ||
| Finally, make sure to add the bytes package to the `import` stanza at the top of `app.go`: |
There was a problem hiding this comment.
| Finally, make sure to add the bytes package to the `import` stanza at the top of `app.go`: | |
| Finally, make sure to add the bytes package to the `import` statement at the top of `app.go`: |
?
|
Minor comments, but looks good. |
Co-authored-by: Jasmina Malicevic <jasmina.dustinac@gmail.com>
This is an automatic backport of pull request #197 done by Mergify.
Cherry-pick of 9883814 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com