Data export fails with copy_file_range: function not implemented
#1445
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1445
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Setup
I use a Docker Compose setup, see: vikunja/frontend#3228
Steps to reproduce
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:
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
Data export failsto Data export fails with `copy_file_range: function not implemented`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).The data export works for me in
0.20.4+31-33f0d0f85a
:)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 aPUT 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 since0.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.
Can you open a new issue for this?