Dashboard

LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test-3-30-2026 : Added testcases to TaskGeneral

LDT-3590 Misc SW Enhancements - SW - 02 - General Aesthetics - 02-S24 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -4
    • +4
    /suite_leahi/tst_main_treatment/test.py
    • -12
    • +7
    /suite_leahi/tst_ultrafiltration/test.py
LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test-3-30-2026 : Added test cases for PersistentAlarm.c file

Aligned the import function

Aligned the import function

Removed <i> from string as per comment

Removed <i> from string as per comment

LDT-3590 Misc SW Enhancements - SW - 02 - General Aesthetics - 02-S24 - Q&R - 15: SIT - Software Integration Tests - Squish Qt

File is removed

File is removed

LDT -3449 Water, Dialysate, and Blood Sampling - SW - 02 - Water sample & Dialysate Checks - Q&R - 15: SIT - Software Integration Tests - Squish Qt

moved this function to tst_headerbar_information_popup as per comment

moved this function to tst_headerbar_information_popup as per comment

LDT-3909 Misc SW Enhancements - SW - 02 - General Aesthetics - Q&R - 15: SIT - Software Integration Tests - Squish Qt

LDT-1804 General Alarm Requirements - SW - 02 - Instructions with new design - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -21
    • +24
    /suite_leahi/shared/scripts/names.py
Post treatement test case

I think these remaining 4 else ifs need to have another && condition that your service is in idle state so that we don't change back into one of these 4 states while a bolus is in progress.

I think these remaining 4 else ifs need to have another && condition that your service is in idle state so that we don't change back into one of these 4 states while a bolus is in progress.

Can we restore the real code here yet? Ask Dara.

Can we restore the real code here yet? Ask Dara.

Why comment this out? fault ID should probably be more specific (i.e. which message payload length is invalid?)

Why comment this out? fault ID should probably be more specific (i.e. which message payload length is invalid?)

LDT-3958 heater control update

    • -15
    • +1
    /firmware/App/Controllers/Heaters.c
Bamboo Commit: Updated Alarms.conf

Bamboo Commit: Copied Alarms table from Alarms folder

Bamboo Commit: Updated MAlarmMapping.cpp

    • -14
    • +20
    /sources/model/hd/alarm/MAlarmMapping.cpp
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

    • -20
    • +14
    /sources/model/hd/alarm/MAlarmMapping.cpp
Merged release/p1b/staging

Merged DENBUG-337

RESOLVED RI: as for the version, we are releasing version 0.5.6 (previous RC was build_1, this is build_3, but build_1 was never promoted to gold). If we need to upgrade the version as well (maybe...

RESOLVED

RI: as for the version, we are releasing version 0.5.6 (previous RC was build_1, this is build_3, but build_1 was never promoted to gold). If we need to upgrade the version as well (maybe because 0.5.6-build_1 was recorded as a released version in you QMS), please let me know and we'll re-release build_3 version as 0.5.7

RESOLVED RI: The sentinel sub-folder (/media/sd-card/cloudsync/sentinel/) is created by the Watchdog._init_() constructor in cloudsync/utils/watchdog.py - it runs os.makedirs(sentinel_dir, exist_o...

RESOLVED

RI: The sentinel sub-folder (/media/sd-card/cloudsync/sentinel/) is created by the Watchdog._init_() constructor in cloudsync/utils/watchdog.py - it runs os.makedirs(sentinel_dir, exist_ok=True) at construction time, so the folder exists before any sentinel file gets written.

RESOLVED RI: It's defined in two places because cs.py and watchdog.py live on opposite sides of a process boundary and don't share a common import. watchdog.py (SENTINEL_PATH) is the producer - it...

RESOLVED

RI: It's defined in two places because cs.py and watchdog.py live on opposite sides of a process boundary and don't share a common import. watchdog.py (SENTINEL_PATH) is the producer - it runs inside the cloud_sync.py app process and writes the sentinel file when a thread can't be recovered. cs.py (SENTINEL_FILE) is the consumer - it's the lightweight launcher that spawns cloud_sync.py and polls for that file to restart it. cs.py is deliberately kept minimal and doesn't import the cloudsync package, so the path is duplicated as a local literal rather than shared.

LDT-3958 resolving merge issues

    • -10
    • +31
    /firmware/App/Modes/ModeGenDialysate.c
Why isn't this TRUE == ?

Why isn't this TRUE == ?

LDT-3958 latest from staging