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_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 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.

Tiffany Mejia
Why do have this defined in two places?

Tiffany Mejia
Which function will create the sentinel sub-folder?

Tiffany Mejia
Please ask for the version update.