consensus

What happened?

In a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:

{"level":"panic","ts":"2022-06-13T14:11:27.870Z","caller":"etcdserver/apply.go:638","msg":"unexpected error during txn","error

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

In working on informalsystems/tendermint-rs#1144, I see that the statesync.fetchers configuration option is serialized as a string. Does it need to be a string? It seems like it should be an integer value.

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

Your question

现在对于线性一致性读是通过 RaftOptions.readOnlyOptions 配置进行全局控制的。 不能针对业务请求来区分，不够灵活。

Your scenes

Your advice

建议 ReadIndexClosure 增加 ReadOnlyOption 来控制当前请求线性一致性的类型。

Here is a rough idea of what this test should do:

• It should be quite similar to the other tests which are currently in place.
• It should isolate a follower node, write a data to the cluster which will cause that node to fall behind into lagging state, but not into snapshotting state.
• It should then spawn a task which will continue to write data to the cluster.
• Just after it is spawne

Sorry for only getting around to looking at this after it was merged, but I think we should remove the NodeID from the ATX. It was only there when we needed to maintain an identity database - now that we don't, we should derive the public key from the signature and do all validations on that (e.g. that the PoST proof validates with this key and that the key we derived from the previous ATX match

https://github.com/paritytech/sub-flood

And more... What might you add? 😁

• Blocked by #2378

As mentioned in [this comment] we temporary allow users to send extra bytes, but we print warning message. This was done to help SDK-developers.

After everything is stabilized we have to remove this and return an error every time something with extra bytes was sent