Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
OpenTodoList
OpenTodoList
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 30
    • Issues 30
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • rpdev
  • OpenTodoListOpenTodoList
  • Issues
  • #214

Closed
Open
Opened Jan 03, 2019 by Martin Höher@mhoeher
  • Report abuse
  • New issue
Report abuse New issue

Implement smarter handling of cache in case of failures during initialization

Currently, when opening the cache fails during initialization, the app is basically rendered useless. We cannot live without the cache - this is currently by design - however, we should handle corruptions of the cache. If e.g. on Windows the user previously had the 32bit version installed and now switches to 64bit, we should allow to dispose the cache and re-populate it.

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
Code task
Assign labels
  • View project labels
Reference: rpdev/opentodolist#214