You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently a --peer-defaultchain option
which can be passed to peer node start which will
setup a testchain. This was used in the past while
work was underway to support creating channels but
at this point it is no longer needed and we should not
have test code in the production path.
This is Part 1 of 2 to fix this. First, we remove
the actual code for creating testchainid but we
leave the CLI flag because the SDK e2e's have it
in their compose cmd.
Change-Id: I7229d647976a5d927dc0c53cfaeebd7f5fa9c811
Signed-off-by: Gari Singh <[email protected]>
logger.Panic("No ordering service endpoint provided, please use -o option.")
190
-
}
191
-
192
-
iflen(strings.Split(orderingEndpoint, ":")) !=2 {
193
-
logger.Panicf("Invalid format of ordering service endpoint, %s.", orderingEndpoint)
194
-
}
195
-
196
-
chainID:=util.GetTestChainID()
197
-
198
-
varblock*cb.Block
199
-
200
-
func() {
201
-
deferfunc() {
202
-
iferr:=recover(); err!=nil {
203
-
logger.Fatalf("Peer configured to start with the default test chain, but supporting configuration files did not match. Please ensure that configtx.yaml contains the unmodified SampleSingleMSPSolo profile and that sampleconfig/msp is present.\n%s", err)
0 commit comments