I'm using TLS on etcd 3.3.12 and have a mix of etcd proxies and masters. The proxies don't seem to honour the --cipher-suites setting, as it ends up with ECDHE-RSA-AES256-GCM-SHA384 despite --cipher-suites=TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 being set.

$ pgrep -laf /usr/bin/etcd
21968 /usr/bin/etcd --listen-client-urls https://0.0.0.0:4000 --adv

Bug Report

What version of TiKV are you using?

I think the description of config max-tasks-per-worker-high in the document is wrong:https://github.com/tikv/tikv/blob/master/docs/V2.1/op-guide/coprocessor-config.md#max-tasks-per-worker-high
https://github.com/tikv/tikv/blob/master/docs/refer

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-

Quorum doesn't return a message error clearly specifying the cause of an error (from a user standpoint) when the transaction manager fails to Quorum (e.g: 400 bad request, ...).

System information

Release: 2.2.3

Expected behaviour

Helpful error message

Actual behaviour

invalid argument 0: json: cannot unmarshal non-string into Go value of type common.Hash

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

Is your feature request related to a problem? Please describe.

Configuration options are not documented on the web site.

Describe the solution you'd like

I need to look at the code (i.e. the *Config classes) or at the Javadoc in order to determine the configuration options. I'd like to have it documented on the website and to be sure that the configuration options match whatever

Description

Now it is in the changelog and release note.

Versions

develop

Additional Information

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

We currently have a generic make target that pulls in the latest protobuf dependencies - documented here. To prevent competing updates to our auto-generated code we should be more explicit. I quite like the documentation here

We are using Ethermint 0.4.0.

Where does the gas that is spent on a transaction go? After doing some simple tests of transferring ether from on account to another, the gas is correctly deducted from the sending account, but I can't figure out which account that goes to.

I would have thought that it would be a validator?

So, I created a miner reward strategy, specifying an account to rece

Overview / Motivation

we want to reduce code duplication in the makefile

The Task

Add a makefile function that returns a bin_path string based on the OS and the bin name provided.

Example:
bin_path(p2p)
on windows will return : pwd/build/p2p.exe
on unix: pwd/build/p2p

Implementation Notes

TODO: Add links to relevant resources, specs, related issues, etc...

Contrib

Previously we relied on github.com/ethereum/go-ethereum/common package to things like Address.

We need to get rid of this reliance and use our own implementation (especially for our internal/common/address.go). If anything is needed from Ethereum, we need to port their code into our package.

• https://github.com/oronsh/raftor

kv_server.cc:156:31: error: ‘class floyd::Floyd’ has no member named ‘DirtyWrite’
Status result = floyd_->DirtyWrite(request.key(), request.value());

kv_server.cc:139:47: error: no matching function for call to ‘floyd::Floyd::GetServerStatus(std::string&)’
bool ret = floyd_->GetServerStatus(value);

lots of bug exists

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

du -h .git/objects/pack/
461M    .git/objects/pack/

git verify-pack and git rev-list --objects --all indicate that this is due to various .exe and .db files that have been added and then deleted to the repository, but are still in its history.

This may not be considered a bug, but it seems weird to have to clone nearly half a GB to get 2MB worth of code.

Per @mtrippled :

The counters parameter to server_info is not documented. You can see what it is by doing rippled server_info counters, or by passing a parameter counters with value true.

Presumably doing this adds diagnostic information, but I'm not sure about the specifics.