CLOUDSYNC-DENBUG-337

CLOUDSYNC-DENBUG-337

Activity on this page:

Line History

Line history chart not available

Line history chart not available

 

Stats

Commits this week: 0
Total Commits: 3,393
Last Commit: 18 Jun
Commits this week: 0

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 
Friday 29 May
8:33 am

Dara Navaei

8:32 am

Dara Navaei

CLOUDSYNC-DENBUG-337_Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views
CLOUDSYNC-DENBUG-337_Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views
8:32 am

Dara Navaei

8:32 am

Dara Navaei

Thursday 28 May
5:30 pm

Dara Navaei and Behrouz NematiPour

5:27 pm

Dara Navaei and Behrouz NematiPour

5:25 pm

Behrouz NematiPour

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

5:25 pm

Behrouz NematiPour

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.

5:25 pm

Behrouz NematiPour

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.

3:09 pm

Behrouz NematiPour

Tiffany Mejia Why do have this defined in two places?

Tiffany Mejia
Why do have this defined in two places?

3:07 pm

Behrouz NematiPour

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

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

3:03 pm

Behrouz NematiPour

Tiffany Mejia Please ask for the version update.

Tiffany Mejia
Please ask for the version update.

9:52 am

Dara Navaei

CLOUDSYNC-DENBUG-337_Release/Denbug 337 Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views P1B Staging
CLOUDSYNC-DENBUG-337_Release/Denbug 337 Whitney Inf Values Not Displaying AS 0 ON The Hcp Portal Views P1B Staging