Usman Saleem

@non-fungible-nelson I've picked up this issue. This resulted in taking out Besu's custom errorprone into its own repo. Also, the class involved, looks like our errorprone check is not always...

While investing this issue, the Besu's custom errorprone checks which were part of Besu codebase and were built and applied in each `build` task, has been moved to its own...

PRs list: - https://github.com/hyperledger/besu/pull/7015 - https://github.com/hyperledger/besu/pull/7016 - https://github.com/hyperledger/besu/pull/7017 - https://github.com/hyperledger/besu/pull/7018 - https://github.com/hyperledger/besu/pull/7019 - https://github.com/hyperledger/besu/pull/7020 - https://github.com/hyperledger/besu/pull/7021 - https://github.com/hyperledger/besu/pull/7024 - https://github.com/hyperledger/besu/pull/7025

Hi @vcolin7 , are there any updates (or workaround) on this issue? Our code is failing on Java 17 as well. ``` final CryptographyClient cryptoClient = vault.fetchKey(config.getKeyName(), config.getKeyVersion()); final byte[]...

@pentiak our code is constructing CryptographyClient is follows: ``` return new CryptographyClientBuilder() .credential(tokenCredential) .keyIdentifier(keyId) .buildClient(); ``` The exception is raised when we perform `cryptoClient.sign(...)` operation. I am not 100% sure...

I'll try to checkout the code over the weekend.

Removed P2 label. Need to reevaluate the bug priority.

@amsmota See https://github.com/hyperledger/besu/pull/7424#issuecomment-2320674559 please.

@amsmota You accidently closed it, I've reopened it and enabled automerge. What you need to do is merge the `main` branch back onto your branch. Once you have up-to-date changes...

@amsmota you don't need to "close" PR, once PR is merged to main, its status will automatically changed.