It is mentioned that there is an error code page for v2 protocol:
https://github.com/etcd-io/etcd/blob/ae7862e8bc8007eb396099db4e0e04ac026c8df5/server/etcdserver/api/v2error/error.go#L16

However, I can't find Documentation/v2/errorcode.md in this repo. Is the comment stale?

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

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

The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

非常感谢大家对 SOFAStack 开源的关注和支持，这是我们前进最大的动力。

收集目的

• 了解 SOFAStack 的使用场景以便更好的规划技术路线
• 聆听社区的不同声音，让 SOFAStack 变得更好
• 吸引更多的开源爱好者参与贡献，共同打造 SOFAStack

收集方式

请按如下参考格式回复本 Issue 进行登记：

• 公司/组织名称：蚂蚁金服
• 地点：中国杭州
• 网址：http://www.antfin.com
• 使用组件及场景：全套金融级分布式中间件
• 联系方式：zhanggeng.zg@antfin.com

展示

我们会定期同步信息至「Awesome SOFA」的用户列表中。

服务

如果您已经在生产环境中使

Description

Now it is in the changelog and release note.

Versions

develop

Additional Information

-----------Chinese-------
把各版本的升级提示移到单独的一个文件夹

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

It's currently stored as a string. It should be stored as a bytearray, and only converted to a string when printed:

https://github.com/spacemeshos/go-spacemesh/blob/8a072181bfe2633d2a90461deb29627c1283706e/common/types/account_state.go#L15

Instead of a single validator (a.k.a. pivot node), the test net_dynamic_hb should pick a subset of validators at random for removal. This will better reflect the [interface](https://github.com/poanetwork/hbbft/blob/742ad7b83a3f613fd9a7b4ff88cfa82b10bd7dd3/src/dynamic_honey_badger/dyn