Skip to content

Major spec update to prepare v0.24.0 for release#2343

Merged
ebuchman merged 15 commits intodevelopfrom
release/v0.24.0
Sep 7, 2018
Merged

Major spec update to prepare v0.24.0 for release#2343
ebuchman merged 15 commits intodevelopfrom
release/v0.24.0

Conversation

@ebuchman
Copy link
Contributor

@ebuchman ebuchman commented Sep 5, 2018

Opening this against develop to facilitate review.

Still need to update some docs but will tag rc0 now.

Awesome work everyone!

@ebuchman ebuchman changed the base branch from master to develop September 5, 2018 23:15
@codecov-io
Copy link

codecov-io commented Sep 6, 2018

Codecov Report

Merging #2343 into develop will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #2343      +/-   ##
===========================================
- Coverage    61.09%   61.05%   -0.04%     
===========================================
  Files          197      197              
  Lines        16302    16302              
===========================================
- Hits          9959     9953       -6     
- Misses        5477     5491      +14     
+ Partials       866      858       -8
Impacted Files Coverage Δ
consensus/replay.go 54.85% <0%> (-7.77%) ⬇️
p2p/peer.go 57.95% <0%> (-1.14%) ⬇️
blockchain/pool.go 66.43% <0%> (+0.69%) ⬆️
consensus/reactor.go 74.89% <0%> (+1.34%) ⬆️

@melekes
Copy link
Contributor

melekes commented Sep 6, 2018

@ebuchman ebuchman mentioned this pull request Sep 6, 2018
- `chain_id`: ID of the blockchain. This must be unique for
every blockchain. If your testnet blockchains do not have unique
chain IDs, you will have a bad time. The ChainID must be less than 50 bytes.
chain IDs, you will have a bad time. The ChainID must be less than 50 symbols.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we allow unicode? Why is it symbols not bytes

Copy link
Contributor

@melekes melekes Sep 6, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

200 bytes (or 50 UTF-8 symbols 4 bytes each)

@ebuchman ebuchman mentioned this pull request Sep 6, 2018
4 tasks
* better overview section
* section on tags
* remove notes about state/concurrency from CheckTx
* incorporate feedback from #2249
* explain how validator set updates effect future blocks
@ebuchman
Copy link
Contributor Author

ebuchman commented Sep 7, 2018

I just pushed a big refactor to the ABCI docs and I'd like to merge it to develop to see it on the staging site - I'll make sure things are basically still functional and then I think we're ready for release. There's still some more feedback to include from #2249 and #2143, but it can happen in hotfixes after the release

@ebuchman ebuchman changed the title Release/v0.24.0 Major spec update to prepare v0.24.0 for release Sep 7, 2018
@ebuchman ebuchman merged commit 246a562 into develop Sep 7, 2018
* move spec/software/abci.md to spec/abci/apps.md and improve it
* move some of app-dev/app-development.md to spec/abci/client-server.md
This was referenced Sep 7, 2018
When `Commit` completes, it unlocks the mempool.

Note that it is not possible to send transactions to Tendermint during `Commit` - if your app
tries to send a `/broadcast_tx` to Tendermint during Commit, it will deadlock.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the "deadlock" the right word? I thought if somebody's trying to send tx during Commit, it will wait until lock gets released (X ms.)

err := mempool.CheckTx(tx, nil)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they send the tx from the Commit method itself, it will deadlock since the mempool lock isnt released until we're done CheckTx

This way the application can determine the initial validator set for the
blockchain.

ResponseInitChain also includes ConsensusParams, but these are presently
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we link an issue here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont think we have one yet

@melekes
Copy link
Contributor

melekes commented Sep 7, 2018

#2354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants