Skip to content
#

consensus

Here are 376 public repositories matching this topic...

fabric
varadgit
varadgit commented Oct 7, 2021

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

JeanGolang
JeanGolang commented Feb 7, 2017

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-
thedodd
thedodd commented Aug 17, 2020

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
go-spacemesh

Improve this page

Add a description, image, and links to the consensus topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the consensus topic, visit your repo's landing page and select "manage topics."

Learn more