Dave Enyeart
Dave Enyeart
It looks like the same issue exists for fabric-chaincode-java, here's the old javadoc publish: https://github.com/hyperledger/fabric-chaincode-java/blob/main/ci/azure-pipelines.yml#L123-L161
@mbwhite @jkneubuh ?
Is anybody still having this issue? I'm not able to reproduce on Fabric v2.5.11 and CA 1.5.15, it works for me and others that I've talked to recently.
Idemixgen was removed from the set of Fabric produced binaries but is still mentioned in ReadTheDocs
@Sayalikukkar I've assigned to you, go ahead and start! I'd recommend remove the content from https://github.com/hyperledger/fabric/blob/main/docs/source/idemixgen.rst and add it to https://github.com/IBM/idemix/blob/main/README.md. This will require a pull request in each repository....
Can you point to the file and code line in question?
In practice the only actor that could do this is the peer admin. If the peer admin is malicious you've got bigger problems. That being said, we would welcome pull...
DCO check failed because the 2nd commit hasn't been signed. See https://github.com/hyperledger/fabric/pull/4969/checks?check_run_id=29433016226
There is an [open issue](https://github.com/hyperledger/fabric/issues/3650) discussing potential update to protos-go-apiv2. Due to some concerns that were raised in that issue, my [latest thinking](https://github.com/hyperledger/fabric/issues/3650#issuecomment-2161393753) was to not proceed with the update....
> > There is an [open issue](https://github.com/hyperledger/fabric/issues/3650) discussing potential update to protos-go-apiv2. Due to some concerns that were raised in that issue, my [latest thinking](https://github.com/hyperledger/fabric/issues/3650#issuecomment-2161393753) was to not proceed with...
Github is still using 22.04 for ubuntu-latest, and is still calling 24.04 'beta' for some reason - https://github.com/actions/runner-images?tab=readme-ov-file#available-images. How do you feel about using 22.04 for a more incremental step...