vorta icon indicating copy to clipboard operation
vorta copied to clipboard

Crash while adding existing repo

Open mwillsey opened this issue 1 year ago • 2 comments

While trying to add an existing borgbase repo to vorta (on a fresh flatpak install), I encountered the following error and was instructed to post an issue.

Traceback (most recent call last):
  File "/app/lib/python3.11/site-packages/peewee.py", line 7253, in get
    return clone.execute(database)[0]
           ~~~~~~~~~~~~~~~~~~~~~~~^^^
  File "/app/lib/python3.11/site-packages/peewee.py", line 4553, in __getitem__
    return self.row_cache[item]
           ~~~~~~~~~~~~~~^^^^^^
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/lib/python3.11/site-packages/vorta/application.py", line 227, in react_to_log
    profile = BackupProfileModel.get(name=context['profile_name'])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/lib/python3.11/site-packages/peewee.py", line 6805, in get
    return sq.get()
           ^^^^^^^^
  File "/app/lib/python3.11/site-packages/peewee.py", line 7256, in get
    raise self.model.DoesNotExist('%s instance matching query does '
vorta.store.models.BackupProfileModelDoesNotExist: <Model: BackupProfileModel> instance matching query does not exist:
SQL: SELECT "t1"."id", "t1"."name", "t1"."added_at", "t1"."repo_id", "t1"."ssh_key", "t1"."compression", "t1"."exclude_patterns", "t1"."exclude_if_present", "t1"."schedule_mode", "t1"."schedule_interval_count", "t1"."schedule_interval_unit", "t1"."schedule_fixed_hour", "t1"."schedule_fixed_minute", "t1"."schedule_interval_hours", "t1"."schedule_interval_minutes", "t1"."schedule_make_up_missed", "t1"."validation_on", "t1"."validation_weeks", "t1"."prune_on", "t1"."prune_hour", "t1"."prune_day", "t1"."prune_week", "t1"."prune_month", "t1"."prune_year", "t1"."prune_keep_within", "t1"."new_archive_name", "t1"."prune_prefix", "t1"."pre_backup_cmd", "t1"."post_backup_cmd", "t1"."dont_run_on_metered_networks" FROM "backupprofilemodel" AS "t1" WHERE ("t1"."name" = ?) LIMIT ? OFFSET ?
Params: ['New Repo', 1, 0]

mwillsey avatar Feb 23 '24 18:02 mwillsey

I was able to reinstall vorta and successfully add the repo. Here's what I did in sequence:

  1. Install vorta flatpak on fresh machine
  2. Try to add repo
  3. It hung, and gnome prompted to to force quit, and I did
  4. Restart vorta, try to add again
  5. Got the above error
  6. Reinstalled vorta from flatpak
  7. Add repo, hangs again (same prompt from gnome), but I just waited, and it eventually succeeded.

mwillsey avatar Feb 23 '24 18:02 mwillsey

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar May 24 '24 02:05 github-actions[bot]

This issue was closed because it has been stalled for 7 days with no activity.

github-actions[bot] avatar May 31 '24 02:05 github-actions[bot]