Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

alarm import/export does not retain sorted order #610

Closed
forrestguice opened this issue Jun 11, 2022 · 1 comment · Fixed by #616
Closed

alarm import/export does not retain sorted order #610

forrestguice opened this issue Jun 11, 2022 · 1 comment · Fixed by #616
Milestone

Comments

@forrestguice
Copy link
Owner

forrestguice commented Jun 11, 2022

Describe the bug
Alarm import does not retain original sorted order (by 'creation date'). When exporting/importing the same list to several devices, each may display a different order.

To Reproduce

  1. Add several alarms if the list is empty.
  2. Sort by 'creation date'. Observe the order of the list.
  3. Export alarms to file.
  4. Clear the alarm list.
  5. Import alarms (from recent export).
  6. Sort by 'creation date'. Observe that the order of the list is now reversed.
  7. Repeat steps 2-5, except sort by 'alarm time' before exporting.
  8. After importing, sort by 'creation date'. Observe that the 'creation date' order is now a reverse of the previous 'alarm time' order.

Expected behavior
The alarm list should retain its 'creation date' order when exporting and importing.

Additional context
The bug originates during export - the list is exported in whatever order it is currently displayed.

Version Info:
Tested with 0.14.6.

@forrestguice
Copy link
Owner Author

@Timo-Fi I found this bug thanks to your comments in #602. I don't think its directly related to that issue (but like a lot of things tangential). There are actually several confounding issues with that alarm list.

It sounds like there is still another bug out there though. One that causes recently added items (whether imported or otherwise) to fail if scheduled for the near future (~10 minutes).

forrestguice added a commit that referenced this issue Jun 11, 2022
sort items by 'creation date' when exporting to file (#610)
@forrestguice forrestguice added this to the v0.14.7 milestone Jun 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant