tendermint

mirror of https://github.com/tendermint/tendermint.git synced 2026-01-06 21:36:26 +00:00

Files

Anton Kaliaev 5f3048bd09 call FlushSync before calling CommitSync

if we call it after, we might receive a "fresh" transaction from
  `broadcast_tx_sync` before old transactions (which were not
  committed).

Refs #1091

```
Commit is called with a lock on the mempool, meaning no calls to CheckTx
can start. However, since CheckTx is called async in the mempool
connection, some CheckTx might have already "sailed", when the lock is
released in the mempool and Commit proceeds.

Then, that spurious CheckTx has not yet "begun" in the ABCI app (stuck
in transport?). Instead, ABCI app manages to start to process the
Commit. Next, the spurious, "sailed" CheckTx happens in the wrong place.
```

2018-01-23 16:56:14 +04:00

txindex

determinisitic linter (#902 )

2017-12-10 17:44:22 +00:00

errors.go

consolidate saveResults/SaveABCIResponses

2017-12-26 19:24:45 -05:00

execution_test.go

state: send byzantine validators in BeginBlock

2017-12-29 11:26:55 -05:00

execution.go

call FlushSync before calling CommitSync