Repository navigation
Offline sender sets the folder, metadata and tags twice - at the beginning and end of a run #815
Description
Looking at the Activity tab for an offline run this is clearly seen:
{{ message }}
Looking at the Activity tab for an offline run this is clearly seen:
Activity
wk9874 commentedon Aug 13, 2025
This is because
_stagingis used in some parts of the code as a full cache of the state of the Run. In offline mode, the getters for properties look inside this dict to find the latest value. This means that it cannot be cleared after it is written to a file, hence the full run is written to a file when anything about it changes, meaning when the status changes to completed the full detail about the run is written to the server again.I propose splitting this functionality into
_cache, which contains all details about the state of the run, and_staging, which contains only updates since the last time the run was written to a file._stagingcan then be cleared each time it is written to a file, fixing this issue