looplab

connected component (strongly connected components). Related algorithms include Kosaraju, Tarjan, Gabow, etc., interested friends can search the relevant introduction. I use the Tarjon algorithm provided by Http://github.com/looplab/tarjan to calculate: 1234567891011121314151617181920212223242526272829303132333435 PackageMainImport("FMT""Github.com/looplab/tarjan")funcMain () {graph:

(t *DemoChaincode) Init(stub shim.ChaincodeStubInterface) pb.Response { // more logics using stub here return stub.Success(nil)}func (t *DemoChaincode) Invoke(stub shim.ChaincodeStubInterface) pb.Response // more logics using stub here return stub.Success(nil)}func main() { err := shim.Start(new(DemoChaincode)) if err != nil { fmt.Printf("Error starting DemoChaincode: %s", err) }} startup process Chaincode first is an ordinary Golang program, whose main method

=0.0.0.0 ports: -"9200:9200" -"9300:9300" logstash: image:logstash:latest command:logstash-f/etc/logstash /conf.d/logstash.conf Volumes: -/logstash/config:/etc/logstash/conf.d ports: -"5001:5000/ UDP " Links: -elasticsearch kibana: build:kibana/ volumes: -./kibana/config/:/opt /kibana/config/ Ports: -"5601:5601" Links: -Elasticsearch #好了命令 can start elk directly, docker-compose up-d. Access to the previous settings of the Kibanna 5601 port can be see

(Stream chaincodemessage) {} } //Generated service-side flow interface type Chaincodesupport_ RegisterServer Interface { Send (*chaincodemessage) error Recv () (*chaincodemessage, error) Grpc. Clientstream }1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 1 2 3-4-5 6 7 8 9 10 11 12 13 14 15 16-17 FSM The FSM is the abbreviation for the finite state machine, which is a third-party library used by the Chaincodesupport service and can be downloaded in GITHUB.COM/

context. Context, opts ... grpc. Calloption) Two methods. After initialization is complete, create a finite state machine structure (FSM,GITHUB.COM/LOOPLAB/FSM). The FSM triggers a state transition based on the received message and the current state, and performs the action set in advance. Peer-side also uses a similar FSM structure to manage message responses. After that, the first GRPC message is sent to the peer using the created GRPC connection: