Data export fails with copy_file_range: function not implemented #1445

New Issue

lluni · 2023-03-24T17:14:20Z

lluni commented

2023-03-24 17:14:20 +00:00

Description

Setup

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

Steps to reproduce

Log in Vikunja
Go to Settings -> "Export your Vikunja data"
Enter valid password and enter
See a green message "Success You've successfully requested your Vikunja Data! We will send you an email once it's ready to download."

Actual behavior

Only the green message is displayed, but there is no email being sent. Also, the following line is logged in the API container:

2023-03-24T16:52:59.127966342Z: ERROR	▶ events/func1 556b Error while handling message bf9e61f9-226f-484b-a63b-c2a4a5759ad9, reason_poisoned=write files/12: copy_file_range: function not implemented, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel,  payload={"User":{"id":1,"name":"[redacted]","username":"[redacted]","created":"2022-12-29T18:22:42Z","updated":"2023-03-23T18:17:35Z"}}

Expected behavior

An email is being sent or an error is being displayed in the frontend.

Other info

When searching for the error I found this and this (1.20 backport) issue in the Go repo, with the second one being fixed in Go version 1.20.2. I assume, only the Go version needs to be updated in the Dockerfile.

Vikunja Frontend Version

0.20.5

Vikunja API Version

0.20.4

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: https://kolaente.dev/vikunja/frontend/issues/3228 ##### Steps to reproduce * Log in Vikunja * Go to Settings -> "Export your Vikunja data" * Enter valid password and enter * See a green message "Success You've successfully requested your Vikunja Data! We will send you an email once it's ready to download." ##### Actual behavior Only the green message is displayed, but there is no email being sent. Also, the following line is logged in the API container: ``` 2023-03-24T16:52:59.127966342Z: ERROR ▶ events/func1 556b Error while handling message bf9e61f9-226f-484b-a63b-c2a4a5759ad9, reason_poisoned=write files/12: copy_file_range: function not implemented, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, payload={"User":{"id":1,"name":"[redacted]","username":"[redacted]","created":"2022-12-29T18:22:42Z","updated":"2023-03-23T18:17:35Z"}} ``` ##### Expected behavior An email is being sent or an error is being displayed in the frontend. ##### Other info When searching for the error I found [this](https://github.com/golang/go/issues/58592) and [this (1.20 backport)](https://github.com/golang/go/issues/58627) issue in the Go repo, with the second one being fixed in Go version 1.20.2. I assume, only the Go version needs to be updated in the Dockerfile. ### Vikunja Frontend Version 0.20.5 ### Vikunja API Version 0.20.4 ### 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 17:14:20 +00:00

lluni changed title from ~~Data export fails~~ to Data export fails with `copy_file_range: function not implemented`

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

konrad referenced this issue from a commit

2023-03-24 18:24:35 +00:00

fix: update xgo in dockerfile to 1.20.2

konrad closed this issue

2023-03-24 18:24:35 +00:00

konrad commented

2023-03-24 18:25:24 +00:00

Good catch! I've pushed an update to the go version used in the docker image in 33f0d0f85a. Please check with the next unstable build if the problem is gone (~45min).

Good catch! I've pushed an update to the go version used in the docker image in https://kolaente.dev/vikunja/api/commit/33f0d0f85a7fdfd509bc8a4aad26df95c064468c. Please check with the next unstable build if the problem is gone (~45min).

lluni commented

2023-03-24 19:39:26 +00:00

The data export works for me in 0.20.4+31-33f0d0f85a :)

The data export works for me in `0.20.4+31-33f0d0f85a` :)

🎉 1

lluni commented

2023-03-24 20:01:41 +00:00

Well, the export worked, but now after re-importing, there seems to be a bug:
Each of the namespaces are shown as having no lists and therefore having no tasks, but when viewing the Upcoming tab, the tasks are shown correctly. 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 should probably create a new issue for this.~~

~~Edit: I just tried running a fresh 0.20.4 instance and trying to import there, but that fails similarly, here the tasks aren't even registered as upcoming tasks.~~

~~Edit: 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.~~

Moved to #1446.

~~Well, the export worked, but now after re-importing, there seems to be a bug: Each of the namespaces are shown as having no lists and therefore having no tasks, but when viewing the `Upcoming` tab, the tasks are shown correctly. 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 should probably create a new issue for this.~~ ~~Edit: I just tried running a fresh 0.20.4 instance and trying to import there, but that fails similarly, here the tasks aren't even registered as upcoming tasks.~~ ~~Edit: 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.~~ Moved to #1446.

konrad commented

2023-03-24 21:08:59 +00:00

Can you open a new issue for this?

👍 1

lluni referenced this issue

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

Broken Vikunja data import #1446

ce72 referenced this issue from a commit

2023-03-28 04:55:06 +00:00

fix: update xgo in dockerfile to 1.20.2

konrad referenced this issue from a commit

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