Skip to content

wrong read if memory is near limit #273

@fmoerl-real

Description

@fmoerl-real

Due to incapability of a sync to movescount, my Ambit 2 did not get the flag, that activities were synchronised. Now, almost 95% of memory usage, the last read of an activity by openambit-cli results in a mix of current and old data, almost 1/3 of my activity was flawed. I can provide the activity if necessary.

To solve this problem, my only option was to use another computer with suuntolink. Sunntolink read the data correctly. So my request is to implement a sync-flag for removing the "please sync to movescount" message, and, more important, to resolve the wrong reading error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions