Hi everyone,
Here’s a brief summary of our weekly *Apache ResilientDB (Incubating)*
community
meeting held on *March 30, 2026* for those who couldn’t attend:

Attendees: Bismanpal Anand, Dakai Kang, Josh Hutton, Junchao Chen, Mohammad
Sadoghi, Shaokang Xie

Brief Summary
The team discussed progress on multiple development tasks, including voting
results for four new members. Bismanpal reported on meetings with potential
contributors Omar and Ahan regarding smart contract implementation, and
updates to the REST contract and GraphQL for smart contract execution. Josh
shared his progress implementing the recovery system in Raft but
encountered failing tests on his system, which Junchao helped troubleshoot
by suggesting Docker. The team also discussed outstanding pull requests,
including ResShare and ResSQL implementations that needed to be completed
and merged.

*Action Items:*

   - Finalize the latest release by getting in touch with IPMC members.
   - Update the second iteration of Architecture Diagram
   - Merge the approved ResShare pull request and attach it to the
   corresponding issue. Also update the ResSQL team with problems in their PR
   - Continue working on the Smart Contract Execution

Candidate Voting Process & Release update
The team discussed the status of voting for four candidates, with Bismanpal
confirming that all votes had been counted and that the ICLA process was
complete. Regarding release, the team is still waiting on one additional
vote to finalize a release. Mohammad suggested sending a reminder email to
the entire team about the outstanding vote rather than a new one.

Smart Contract Development Updates
Bismanpal updated the team on recent meetings with Omar and Ahan regarding
smart contract work, including updates to the REST contract and GraphQL for
smart contract execution. He noted that while basic contract functions,
such as balance initialization and transfers, are working, the current
implementation lacks persistent account memory, which needs to be addressed
before further development.

Pull Request Merge Discussion
The team discussed merging two pull requests, with one already approved and
ready to be merged. Junchao identified issues with the ResSQL request,
including a license problem that needs to be addressed with the respective
team. Bismanpal agreed to handle the license issues and merge the pull
request once complete. Mohammad suggested including the completed items in
the next release and confirmed that multiple items have been added to the
upcoming release plan.

Bazel Tests Configuration Issues
Josh reported issues running Bazel tests on his Windows Subsystem for Linux
machine, where 12 out of 42 tests failed. Junchao suggested using Docker
instead of WSL and mentioned that some students had previously run tests
successfully on Docker in Windows. The team discussed potential system
configuration issues and troubleshooting steps.

Recovery Code Test Failures Discussion
The team discussed technical issues with test failures in the recovery
code. Josh identified a null-pointer issue in the storage value during
recovery tests, which Junchao explained was expected behavior, since the
test should skip when storage is null. Junchao agreed to investigate and
fix the test failures later, while Josh indicated he could work around the
issues by skipping affected tests while developing his own recovery version
for Raft.
-
Best,

*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)

Reply via email to