Lots of 'warning: uncommitted changes' in offline mode

[wk9874]

with Run(mode='offline') as myrun:
    myrun.init(name="test_artifact_retrieval", folder="/my/test/2", tags=["my_tag_1"], metadata={"my_1": 1})
    myrun.save_file("upload.py", category="code", metadata={"my_test": True})
    myrun.save_file("test.py", category="input", metadata={"my_test": True})
    myrun.update_tags(["my_tag_2"])
    myrun.update_tags(["my_tag_3"])
    myrun.update_metadata({"my_2": 1})
    myrun.update_metadata({"my_2": 2, "my_3": 3})
    myrun.create_metric_threshold_alert(
        name="my_test_alert_2",
        metric="test_metric",
        threshold = 20.0,
        rule = "is above",
        description = "dddh"
    )
    print(myrun._sv_obj.alerts)

Gives...

WARNING:simvue.Run:Uncommitted change found for attribute 'status'
WARNING:simvue.Run:Uncommitted change found for attribute 'tags'
WARNING:simvue.Run:Uncommitted change found for attribute 'tags'
WARNING:simvue.Run:Uncommitted change found for attribute 'alerts'
WARNING:simvue.Run:Uncommitted change found for attribute 'alerts'

Why do I see these? Changes seem to be being committed to offline cache as expected...

[wk9874]

This is because of the staging_check parameter which is designed to check if there have been locally made changes to the value of an attribute when getting it. Eg if you did:

with Run() as run:
    run.tags = ["tag"]
    tags = run.tags

It would give you this warning, since you have locally committed changes and then try to retrieve values from the server. But in offline mode, all changes are added to the staging dict until sent, which means youll get that warning regularly. Just need to add a 'if offline; return' statement into this dict, as the warning is not relevant

[wk9874]

Fixed in v2.0.0a2