...
| Excerpt |
|---|
|
Recording of Call: 20220412 Indy Contributors Call Recording.mp4
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
...
- Stephen Curran
- Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
- Char Howland
- Lynn Bendixsen
- Mirko Mollik
- Paul Bastian
- Sebastian Schmittner (EECC) <sebastian.schmittner@eecc.de>
- Richard Esplin
- Robin Klemens
- Philipp Schlarb (esatus AG) <p.schlarb@esatusschlarb@esatus.com>com>
- Artur Philipp
- Christian Bormann (Robert Bosch GmbH) <ChristianCarl.Bormann@de.bosch.com>
...
- Before the meeting: "did:indy" DID Method
- Separate meeting held one hour prior to this one.
- Meeting format changes:
- did:indy DID Method Specification call to be conducted as needed within the Indy Contributors call – no longer a separate weekly call
- Indy Contributors call moving back to starting at 8:00 Pacific (fixed) / 17:00 CET (usually) and will once again be scheduled for 1 hour
- Update on CI/CD Update and Ubuntu Upgrade: Status Document
Indy Shared GHA RepoStatus colour Green title New - Updates being made across all repos to organize the GHAs into a single repository (indy-shared-gha), and dependent updates being made to all indy repos
- Indy-Plenum Status:
- Done, 16.04, 20.04, Jenkins and GHA
- Indy-Node Status:
- Done, 16.04, 20.04, Jenkins and GHA
- One 20.04 running in the IDUnion network of 16.04 nodes
- Preparing and executing the automated release process.
- indy-test-automation Status:
- Working systemd image for 20.04, but the tests are not fully tested because of permissions handling decisions to be made ( after GHA work completed) – client messages not getting to the server.. 20.04 requires root where 16.04 doesn't and we want to confirm that to be the case.
- There might be Seems like there is a solution in the indy-node-container work. To be checked with Robin Klemens.
- indy-node-container (moved to Hyperledger) and GitPod tools available (node and plenum)
- Indy-SDK build progress
- Unblocked – builds are going and PRs are being reviewed (and rebasing PRs).
- How are we going to work through this issue and upgrade the various networks?
- Concern - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
- Robin has the details of what tests have been run and what observations have been done. See Hack MD document with some details.
- Perhaps because of libsodium v18 and v23.
- It might also be a ledger corruption issue, perhaps with the lead node having corruption issues and then propagating those issue.
- Can we get the indy-node-container folks run tests with a mixed environment of nodes
- Presentation on the indy-node-container repo / project by Sebastian Schmittner
Future Calls
- Richard Esplin at Avast can get help answering questions about Plenum. Tag him on Discord with your question.
- Blog post on troubleshooting an Indy network.
Future Calls
- GDPR and the right to be forgotten – mitigations and approaches.
- Dealing with Indy Node DoS attacks.
- Issues that could impact indy-node on 20.04
- indy-sdk: needs an upgrade to OpenSSL 1.1 to properly support Ubuntu 18.04/20.04. For indy-node, just using indy-sdk as is.
- Multiple libsodium versions could impact consensus – intermittent issue on a mixed network.
- Plans for a new Indy-SDK release?
- A few people from the community have asked.
- The most recent request has been for a release to include this feature; https://github.com/hyperledger/indy-sdk/pull/2400
- Status of Indy-SDK
- Statement on the future of the Indy SDK: PR 2329
- Plans for future of Indy CLI (move to Indy VDR?)
- Indy SDK in test for Indy Node (move to Indy VDR?)
- Status of GitHub Actions for the Indy-SDK
- Indy bugs
- Using GitHub tags "Good First Issue" and "Help Wanted"
- Node 1490: problems with large catch-up
- Plenum 1506: view change message consensus calculation error