RuView: Calibration Deadlock Fixed on Sensing Nodes

A single fix addresses a deadlock that prevented field-model calibration from ever starting on live sensing nodes, keeping devices permanently stuck in an uncalibrated state. The bug was traced to two gating conditions in the calibration pipeline that each depended on the other.

Duration: PT1M52S

Episode overview

This episode is a short developer briefing from RuView.

It explains recent repository work in plain language.

  • Show: RuView
  • Published: 2026-07-18T06:03:40Z
  • Audio duration: PT1M52S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning. It's July 18th, 2026, and this is RuView.

Today's activity is small in volume but significant in impact: one pull request that fixes a deadlock stopping calibration from working at all on deployed sensing hardware.

The core theme here is a classic two-gate deadlock. In PR 1343, developer rjperry36 traced a bug where the sensing server's calibration endpoint looked alive but never actually did anything. On a real ESP32-S3 deployment, the status would report "uncalibrated" with a frame count stuck at zero — no matter how long…

The root cause: calibration start creates the field model in an uncalibrated state, but the per-frame feed that's supposed to populate it — the "maybe feed calibration" function in the field bridge — only fed data while the model was already calibrated. Each side was waiting on the other. It's the kind of bug that's…

The fix touched several connected areas — the sensing server fork, deployment configs for QNAP, Docker Compose, and the CSI handling — suggesting the calibration path is wired through multiple layers of the deployment stack, not just an isolated module. That's worth remembering: calibration logic isn't…

What's next: with the deadlock…

Nearby episodes from RuView

  1. Health Check Latency Fix
  2. Community Fixes Land, Publish Pipeline Unblocked
  3. Weekly Recap - Security Hardening and Firmware Reliability
  4. Closing the Gaps in Sensing Server and Firmware
  5. Closing the Open-Door API Gap
  6. Sensing Pipeline Catches Up to the Hardware
  7. Firmware Reality Check
  8. Reliability Fixes and Housekeeping