KernelCI Weekly Newsletter (Week 50)

**Summary**

The issues with KCIDB submissions have been largely resolved, though
KCIDB is still experiencing minor problems with large batches (should
not cause data loss). We continue to monitor the situation closely.

This week, we also began planning a redesign of the storage subsystem.
The goal is to improve performance and reliability while providing
artifact storage for both KCIDB and partner CI systems. Since these two
subsystems require significant work, most other features are on hold
until their completion.

**Known Issues**

- `/latest/docs` and `openapi.json` are currently returning a 500
error. We are investigating the issue.

### Key Updates

- **Storage Subsystem Design Proposal**  
  A design proposal for the storage subsystem has been drafted:  
  [Storage Subsystem Design
Proposal](https://gist.github.com/nuclearcat/2d34f8266ccd1b8356bd993eadcf2eed
)  
  Feedback and suggestions from the community are welcome at the weekly
meeting and via the mailing list.

- **New Pub/Sub Subsystem Design**  
  Work is underway on a new Pub/Sub subsystem to address fundamental
issues with the current implementation, including non-guaranteed
message delivery and the lack of load-balancing features.  
  - The new subsystem will use Redis Streams as its foundation.  
  - It will be backward-compatible, requiring no API changes, enabling
seamless migration for clients.

- **Experimental Features in kci-dev**  
  The `kci-dev` team has started implementing experimental features for
retrieving results from the Dashboard API. Details can be found here:  
  [GitHub Issue #57](https://github.com/kernelci/kci-dev/issues/57)

- **Re-enabling ARM64 QEMU Support**  
  Efforts are ongoing to re-enable ARM64 QEMU support.

- **Buildroot Rootfs Fixes**  
  Long-pending fixes for Buildroot rootfs (pending for two years) are
being addressed.

- **Dashboard Improvements and Fixes**  
  As always, continuous improvements and fixes are being made to the
Dashboard.