2-week sprint started Jan. 7. Priority is platform stability, bug fixes, and feature specification.
RNode v0.8.2 released on Jan. 7. At a high level this release delivers bug fixes and optimizations contributing to bugs related to platform stability, expanded test coverage for Casper, and a new implementation of the metrics API to benefit debugging, reporting, and RNode operators. Please see RNode-0.8.2 release plan for more details.
Mercury requirements and acceptance criteria
Ongoing effort to ensure completeness of feature-based user stories in the Mercury features doc (https://github.com/rchain/rchain/blob/dev/docs/features.md). We have tooling in place to show the status of the definition of the feature (Can we describe a test scenario to demo the feature?) and the status of the feature's completeness if the test is implemented. Demo of tool.
Implementation of RhoSpec complete. This is a class that collects failures from Rholang tests and reports them as scalatest failures. Next step is to complete work so we can use this with TestResultCollector in Casper tests.
Bug investigation that looked like an issue with validator bonding, and now appears to related either to the code or the algorithm. We have a unit test to recreate the issue and investigation is underway. Plan is to try a fix to the code: changing the assertion so that all blocks are the same instead of ensuring there is only one block in the list.
RCHAIN-2805Getting issue details...STATUS
Completing work for stream API on client queue with retries. Last PR in review.
RCHAIN-1904Getting issue details...STATUS
PR in review to stop receiving stream blobs if they don't fit in memory.
RCHAIN-1615Getting issue details...STATUS
Updates to DAG grapher to group blocks by validator. This tool has been very helpful in debugging.
Profiling of RNode in progress.
RCHAIN-2765Getting issue details...STATUS