Stabilization Testing | Züs Weekly Debrief (July 20, 2022)

Clarke McMakin

October 31, 2022

Happy Wednesday everyone, I hope you have had a good week so far. This week is dev focused as we continue to round out our plans for the upcoming releases of new content. There is a focus on community interactions. Right now many resources are going towards stabilization testing including byzantine testing and chaos testing. The marketing and biz dev teams are in full swing. They look forward to introducing themselves and their work in the coming future. Let’s take a look at this week’s tech updates.

Development Team Updates

The blockchain team closed 10 PRs and 8 issues on the Züs repo. They addressed several types of issues including API endpoints, a blockchain stability issue mentioned in last week’s update, and testing updates. The team fixed several intertwined issues that would cause the blockchain to get stuck, mainly stemming from a series of processes that would put excess strain on sharders’ resources. In this fix, the team also optimized the state prune process which helps clean up information stored in the node. This is an important fix as it overall enhances the stability of the blockchain network and prevents stalling of the network in live scenarios.

Updates to APIs were made to improve naming and add new filters, further rounding out the ability for users, enterprises, and service providers to pull important information from the network. The team removed the ability for a client allocation to have unbound size. Foreign keys and indexes were added to ReadMarker and WriteMarker tables in order to speed up the query for users/write actions to their allocations. The team removed unused code and added more unit tests for the user table. The team implemented updated info streams for conductor test status as well as moved unneeded zproxy from CI/CD.

Stabilization Testing

During recent stabilization testing, the team detected and implemented a fix for a fault tolerance test failure. This PR is undergoing work by the team to address potential issues that could arise that would put the network at risk. This emphasizes the importance of the robust testing network the team has built out to identify potential issues. The team plans to implement chaos testing into the test environment alongside load testing they will conduct in the coming week.

Blobber Updates

The blobber and gosdk team continue to provide support in other departments and with UI implementation. We saw a total of 4 PRs closed. The team has been putting in maximum effort to round out our various applications, including the block explorer, storage, and wallet applications. The team removed unneeded zproxy from CI/CD, converted GRPC integration tests to run as unit tests, and implemented sending requests concurrently with goroutine instead of in consecutive order.