Added java codgen scripts #16
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…table) 1. This was forced through the domino effect of webpki related security vulnerabilities that made it important for us to upgrade some dependencies which on the other hand did not work with the slightly older rust compiler that the dev container had had. Relevant links for the vulnerabilities (this is not a fix yet) - https://github.com/hyperledger/cacti/security/dependabot/762 - GHSA-8qv2-5vq6-g2g7 Skipping the CI because it's just a development environment change. [skip ci] Signed-off-by: Peter Somogyvari <[email protected]>
- Make not critical connector API private. This will allow easier refactors
in the future. Most of the fields were used for testing purposes anyway.
- Change naming of some methods to match persistence-ethereum plugin.
Signed-off-by: Michal Bajer <[email protected]>
1. No other changs in the test case - just what was strictly necessary to make it work with Jest. 2. Also updated the configuration files of the test runnres in the CI so that the test case gets ignored by tape and included by Jest (the oppositve was true/necessary prior to this change) [skip ci] Signed-off-by: Peter Somogyvari <[email protected]>
jagpreetsinghsasan
force-pushed
the
jagpreetsinghsasan/issue393
branch
from
e80cc63 to
db7c8e8
Compare
- Add test suite for geth-test-ledger package. - Add new test suit to CI - It was initially proposed in hyperledger-cacti#2588, I've added some cleanups and improvements. - Run codegen, update missing deps, sort package.json, fix type in socketio-test-setup-helpers, to fix some CI. Closes: hyperledger-cacti#2579 Co-authored-by: Tomasz Awramski <[email protected]> Signed-off-by: Michal Bajer <[email protected]>
…path 1. Upgraded tonic, prost and tokio to the latest and greatest of versions which was necessary because one of their transitive dependencies being affected by the GHSA-8qv2-5vq6-g2g7 vulnerability. 2. These upgrades also forced our hand in terms of bumping up the rust edition from 2018 to 2021 and upgrading the rust compiler to v1.74. 3. fix(relay): update the code for tonic 0.10.2 4. fix(relay): upgrade rust docker image tag to 1.69.0 Depends on https://github.com/hyperledger/cacti/pull/2916 (which upgrades the rust compiler in the dev container) Co-authored by: Sandeep Nishad <[email protected]> Signed-off-by: Peter Somogyvari <[email protected]> Signed-off-by: Sandeep Nishad <[email protected]>
…S functions The Weaver Fabric interoperation-node-sdk used the "aes-128-ctr" algorithm in a hardcoded manner for asymmetric encryption/decryption. 128-bit AES, though secure for classical computing, is quantum-unsafe. So an option is added to use "aes-256-ctr" on demand. The "aes-128-ctr" algorithm is still supported because many signing keys, typically those used in the Fabric testnets, have embedded elliptic curve parameters with key length 16 bytes, and those still need to be supported. Signed-off-by: VRamakrishna <[email protected]>
…ting identity mgmt Partially reverting changes made in https://github.com/hyperledger/cacti/pull/2901. These changes made the IIN Agent chaincode operations fail. Also fixed typos and formatting in the docs. Signed-off-by: VRamakrishna <[email protected]>
…tnet Signed-off-by: VRamakrishna <[email protected]>
Modified the SDK functions to be compatible with the Weaver Fabric Interoperation Chaincode. Signed-off-by: VRamakrishna <[email protected]>
…tatus and claim status Signed-off-by: Sandeep Nishad <[email protected]>
…files Signed-off-by: Sandeep Nishad <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
…version as 1 Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
Signed-off-by: jagpreetsinghsasan <[email protected]>
jagpreetsinghsasan
force-pushed
the
jagpreetsinghsasan/issue393
branch
from
db7c8e8 to
5055315
Compare
Signed-off-by: jagpreetsinghsasan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: jagpreetsinghsasan [email protected]Pull Request Requirements
[ ] Rebased onto
upstream/mainbranch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.[ ] Have git sign off at the end of commit message to avoid being marked red. You can add
-sflag when usinggit commitcommand. You may refer to this link for more information.[ ] Follow the Commit Linting specification. You may refer to this link for more information.
Character Limit
[ ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[ ] Commit Message per line must not exceed 80 characters (including spaces and special characters).
A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.