Status Update
August 28, 2017
Status Updates (August, 2017) > August 28, 2017
Weekly Development Report
CSL CORE
Here's the latest from the core team: This week the team concentrated on working out internal fixes to the core (nothing critical). Most of these fixes were sanity checks. Also, some tooling for technical operations was addressed. Reporting review was postponed, but it is not deemed critical. Also, Test stake locking was worked on. Manual testing is not finished yet and has been postponed.
DAEDALUS
This week the team successfully implemented the Exporting a wallet to a file and importing a wallet from the file functionality. However, this feature remains not merged due to some changes that are required on the backend. “About screen”, invoked from the system menu, was introduced. Screen for including or excluding transaction fees from the entered amount on Ada send form was prepared and updates to the endpoints were specified. The endpoint is still not done, so this feature was not merged.Work on removing Client API from Daedalus was started and the goal for this sprint was achieved by building a working prototype of direct usage of HTTP API endpoints with TLS secured communication and Flow type definitions.Logging to a remote log management service was improved by sending logs directly using a custom logging implementation instead of tailing the log file from the hard drive.
MIDDLEWARE
The team successfully finished implementing the Resubmitting of transaction functionality. QA was started on unable to send transaction (spending password hashing changed), fixing installers. Fees calculation improvements are still a work in progress. Furthermore, the team spent time on adding component tests
EXPLORER
The team has timestamp reimplemented and merged. Also, Serialization problems with hashing have been fixed.
BENCHMARKING
The team found a race condition in the current code that caused nodes to ignore 5-10% of incoming transactions. The Benchmarking team worked with the Core team to solve this via more rigorous locking, and will, in the coming week, improve the lock to avoid an adverse effect on block processing.
More issues in the staging cluster were found and fixed. These issues were a result of integrating networking changes with the cardano codebase. Those issues decreased the chain quality on the staging cluster. Now that they are resolved, perfect chain quality has been observed.
With help from DevOps, the team made progress towards setting up experiments that will allow to fix the networking policies on the relay nodes. In particular, the team wants to determine the transaction rate that the core cluster can handle, and apply backpressure accordingly. Additionally, the team will probe the ability of relays to serve a large number of edge nodes, so that they will be in a position to determine the number of relays that should be run.
DEVOPS
This week the team:
- Fixed the CI issues regarding timeouts
- Refactored stack2nix to speed up the process by factor of 2 and fix some of the issues (build tooling)
- The week has seen various fixes to staging chain quality
- Benchmarks now have a stable chain, working on getting the transaction generator to run
- Managed cloud DNS hosting related work is blocked on communication and requires the involvement of other teams.
MAJOR GOAL ASSESSMENTS
Testnet 5 release
The week saw an increase in tickets, due to the issue with block syncing. A sum of 35 support tickets have been created.
The top most reported issues were:
- Issue with block synchronization: 29
- Issue with redemption: 3
- Daedalus bug: 1
- Question about mainnet launch: 1
- Cannot connect to the network: 1
Mainnet Release
Following a all hands meeting, a new timeline for launch has been agreed upon.