pfi79

@bstasyszyn @fqutishat can you approve my PR?

@tock-ibm can be closed as corrected.

> unfortunately, this flake is still alive.... Yes, I agree, unfortunately. After restarting an orderer other orderers do not see it because of backoff Here's a [fix](https://github.com/hyperledger/fabric/pull/4610) for that. Please...

@tock-ibm Why do you want to do this? What problem in the fabric will it solve?

> Thinking about it, there is also another policy we could easily implement, in which the peer specifies the ordering-org it trusts and wants to pull blocks from. @pfi79 @yacovm...

> I think what you get is lower costs. > > Since in a multi cloud deployment, the account pays for traffic sent from the server, but not for traffic...

I'll add an observation: - There is a package A, it has 1 file and it has one interface. When this package gets into testing, it seems that go adds...

@thanm If it helps, but it seems to me that it happened because the covervars.go file appeared in the source cache of package “c” and the test was built with...

@thanm alas, we have not fixed the problem with version go 1.23. I tweaked your example a bit to make it similar to our case. https://go.dev/play/p/x8RrtA-p9l2 ``` go test -coverpkg=./......

@dmitshur @thanm @seankhliao the error has not been corrected. Please tell me, will you fix it or do something about it?