-
Updated
Nov 12, 2021 - Go
consensus
Here are 376 public repositories matching this topic...
-
Updated
Nov 12, 2021 - Rust
-
Updated
Nov 9, 2021 - Java
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-
-
Updated
Oct 20, 2021
-
Updated
Sep 30, 2021
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
-
Updated
Sep 15, 2021 - Go
-
Updated
Oct 29, 2021 - Java
-
Updated
Oct 9, 2021 - C++
-
Updated
Jul 17, 2020 - C++
-
Updated
Nov 12, 2021 - Go
-
Updated
Aug 10, 2021 - Rust
-
Updated
Aug 13, 2020
-
Updated
Jun 15, 2021 - Go
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
-
Updated
Oct 7, 2020 - Go
-
Updated
Nov 12, 2021 - Java
-
Updated
Jul 12, 2017 - Java
-
Updated
Sep 28, 2021 - C++
-
Updated
Oct 25, 2021
Description
The app doesn't close when pressing the CTRL-C hotkey immediately after start. Pressing it again and again doesn't change the behavior
Steps to reproduce
- Run
go-spacemesh - Immediately press
CTRL-C
Actual Behavior
Th
-
Updated
Jan 4, 2020 - C++
-
Updated
Nov 8, 2021
-
Updated
Aug 13, 2018 - JavaScript
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
Improve this page
Add a description, image, and links to the consensus topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the consensus topic, visit your repo's landing page and select "manage topics."
When installing a new chaincode on the peer you do get the package id of the chaincode which is good... this allows customers to use that data to go through the approve/commit steps.
However the issue is when they are reinstalling an existing chaincode there is nothing in the response to indicate the package id(hash). Install in that case returns a message that the chaincode already exists. We