Broken Vikunja data import #1446

New Issue

lluni · 2023-03-24T21:41:36Z

lluni commented

2023-03-24 21:41:36 +00:00

Description

Setup

I use a Docker Compose setup, see: vikunja/frontend#3228

Steps to reproduce

Log in Vikunja
Export your Vikunja data
Import your data into Vikunja

Expected behavior

The frontend shows "Everything was migrated successfully." with a refresh button and all the imported data is available.

Actual behavior

The frontend shows "Everything was migrated successfully." with a refresh button, but the namespaces are shown as having no lists and therefore having no tasks, but when viewing the Upcoming tab, the tasks are shown correctly.

Additional info

I am also not able to create any new lists for the imported namespaces, the frontend shows a "Error Not found" message and the API container logs a PUT 404.

Maybe this has something to do with still being on the unstable build (I don't know if there has been any data restructuring since 0.20.4)? I tried running a fresh 0.20.4 instance and trying to import there, but that fails similarly, there the tasks aren't even registered as upcoming tasks.

I noticed that after trying to delete the imported namespaces and reloading the page, two namespaces reappear with some remaining tasks showing in the "Upcoming" tab which then need to be deleted again.

Actually, I didn't expect Vikunja to wipe user data when exporting the data. I expected it more to be some kind of "local backup" possibility.

I haven't yet tested this bug on the demo site.

Vikunja Frontend Version

0.20.5

Vikunja API Version

0.20.4+31-33f0d0f85a

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description ##### Setup I use a Docker Compose setup, see: vikunja/frontend#3228 ##### Steps to reproduce * Log in Vikunja * Export your Vikunja data * Import your data into Vikunja ##### Expected behavior The frontend shows "Everything was migrated successfully." with a refresh button and all the imported data is available. ##### Actual behavior The frontend shows "Everything was migrated successfully." with a refresh button, but the namespaces are shown as having no lists and therefore having no tasks, but when viewing the Upcoming tab, the tasks are shown correctly. ##### Additional info I am also not able to create any new lists for the imported namespaces, the frontend shows a "Error Not found" message and the API container logs a PUT 404. Maybe this has something to do with still being on the unstable build (I don't know if there has been any data restructuring since 0.20.4)? I tried running a fresh 0.20.4 instance and trying to import there, but that fails similarly, there the tasks aren't even registered as upcoming tasks. I noticed that after trying to delete the imported namespaces and reloading the page, two namespaces reappear with some remaining tasks showing in the "Upcoming" tab which then need to be deleted again. Actually, I didn't expect Vikunja to wipe user data when exporting the data. I expected it more to be some kind of "local backup" possibility. I haven't yet tested this bug on the demo site. ### Vikunja Frontend Version 0.20.5 ### Vikunja API Version 0.20.4+31-33f0d0f85a ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

lluni added the

kind/bug

label 2023-03-24 21:41:36 +00:00

lluni referenced this issue

2023-03-24 21:42:17 +00:00

Data export fails with `copy_file_range: function not implemented` #1445

lluni commented

2023-03-24 21:45:25 +00:00

I forgot to add some screenshots, so here they are:

I forgot to add some screenshots, so here they are: ![image](/attachments/d41cfa59-d235-4e41-babd-1ee795d2f93f) ![image](/attachments/1cbeca68-8579-4e5f-8534-cd511aab9a20)

image.png

10 KiB

image.png

116 KiB

konrad commented

2023-03-24 22:10:01 +00:00

There actually have been significant changes to the data format.

Did you create the export with the same version you used to import it?

Are you able to export and import on 0.20.4?

Can you check the json file in the zip file? Does it have all lists and tasks?

Actually, I didn't expect Vikunja to wipe user data when exporting the data. I expected it more to be some kind of "local backup" possibility.

Did it remove existing tasks and lists? It should definitely not do that, it's meant as a way to back up your data, as you guessed.

There actually have been significant changes to the data format. Did you create the export with the same version you used to import it? Are you able to export and import on 0.20.4? Can you check the json file in the zip file? Does it have all lists and tasks? > Actually, I didn't expect Vikunja to wipe user data when exporting the data. I expected it more to be some kind of "local backup" possibility. Did it remove existing tasks and lists? It should definitely not do that, it's meant as a way to back up your data, as you guessed.

lluni commented

2023-03-24 22:23:46 +00:00

Did you create the export with the same version you used to import it?

Yes, both on version 0.20.4+31-33f0d0f85a.

Are you able to export and import on 0.20.4?

Well, I can't export anything on 0.20.4 because of #1445.

Can you check the json file in the zip file? Does it have all lists and tasks?

I didn't check the format itself, but I could Ctrl+F all list names, so they seem to have been exported (somewhat?) correctly.

Did it remove existing tasks and lists?

If I remember it correctly, ~~everything~~ my lists and tasks were wiped after exporting.

> Did you create the export with the same version you used to import it? Yes, both on version `0.20.4+31-33f0d0f85a`. > Are you able to export and import on 0.20.4? Well, I can't export anything on `0.20.4` because of #1445. > Can you check the json file in the zip file? Does it have all lists and tasks? I didn't check the format itself, but I could Ctrl+F all list names, so they seem to have been exported (somewhat?) correctly. > Did it remove existing tasks and lists? If I remember it correctly, ~~everything~~ my lists and tasks were wiped after exporting.

konrad commented

2023-03-26 13:47:20 +00:00

If I remember it correctly, everything my lists and tasks were wiped after exporting.

I could not reproduce this on the latest unstable build. Can you reproduce it on try?

> If I remember it correctly, everything my lists and tasks were wiped after exporting. I could not reproduce this on the latest unstable build. Can you reproduce it on [try](https://try.vikunja.io)?

lluni commented

2023-03-26 14:21:37 +00:00

The https://try.vikunja.io/ instance doesn't seem to have a mailer, that's why I've just tested it again on both FE/BE unstable versions 0.20.5+93-cc519e6773/0.20.4+37-84c3d0ef6d. I can't seem to be able to reproduce the export wipe and also the broken import bug.

I guess, the API/DB was somehow in some unique weird state which caused both bugs...
I think, this issue can be closed, if they can't be reproduced.

(Btw, luckily I've only recently started actively using Vikunja, so it was feasible to just create all tasks manually again on a fresh install.)

The https://try.vikunja.io/ instance doesn't seem to have a mailer, that's why I've just tested it again on both FE/BE unstable versions `0.20.5+93-cc519e6773`/`0.20.4+37-84c3d0ef6d`. I can't seem to be able to reproduce the export wipe and also the broken import bug. I guess, the API/DB was somehow in some unique weird state which caused both bugs... I think, this issue can be closed, if they can't be reproduced. (Btw, luckily I've only recently started actively using Vikunja, so it was feasible to just create all tasks manually again on a fresh install.)

konrad commented

2023-03-26 14:28:28 +00:00

Awesome, please ping back if this happens again.

konrad closed this issue

2023-03-26 14:28:28 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:31 +00:00

chore(deps): update dependency esbuild to v0.14.14 (#1446)

Sign in to join this conversation.