Setting progress causes the item to be marked as done instantly #1681

Open
opened 2024-01-09 10:09:52 +00:00 by hboetes · 11 comments

Description

Setting progress on a task causes the task to immediately getting marked as done. After marking it undone, the task keeps getting marked as done a few seconds later.

Vikunja Frontend Version

0.22.0

Vikunja API Version

0.22.0

Browser and version

Firefox 121

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Setting progress on a task causes the task to immediately getting marked as done. After marking it undone, the task keeps getting marked as done a few seconds later. ### Vikunja Frontend Version 0.22.0 ### Vikunja API Version 0.22.0 ### Browser and version Firefox 121 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
hboetes added the
kind/bug
label 2024-01-09 10:09:52 +00:00
Owner

Is that reproducible consistently across all browsers?

If you can't reproduce it on the demo, that might indicate it's already fixed (the demo runs the last unstable build).

Is that reproducible consistently across all browsers? If you can't reproduce it on the demo, that might indicate it's already fixed (the demo runs the last unstable build).
Author

Thanks for your reply, Konrad.

Do you see any problems, updating a production server running 1.2.2 to the latest unstable?

Thanks for your reply, Konrad. Do you see any problems, updating a production server running 1.2.2 to the latest unstable?
Author

I can reproduce the problem with at my colleague's computer and mine, both running Firefox 121.

For testing purposes I've created a snapshot, upgraded to the latest version, reloaded the window until it told me to reload the window, and then I still can reproduce the problem. After which I restored the snapshot, so we're running 0.22.0 again.

I can reproduce the problem with at my colleague's computer and mine, both running Firefox 121. For testing purposes I've created a snapshot, upgraded to the latest version, reloaded the window until it told me to reload the window, and then I still can reproduce the problem. After which I restored the snapshot, so we're running 0.22.0 again.
Owner

For testing purposes I've created a snapshot, upgraded to the latest version, reloaded the window until it told me to reload the window, and then I still can reproduce the problem. After which I restored the snapshot, so we're running 0.22.0 again.

Do you mean the :latest docker tag? That's the latest release (which is 0.22). Use unstable for the mentioned unstable build.

> For testing purposes I've created a snapshot, upgraded to the latest version, reloaded the window until it told me to reload the window, and then I still can reproduce the problem. After which I restored the snapshot, so we're running 0.22.0 again. Do you mean the `:latest` docker tag? That's the latest release (which is 0.22). Use `unstable` for the mentioned unstable build.
Author

I use the package as downloaded from the mirror. I rather configure things myself.

I use the package as downloaded from the mirror. I rather configure things myself.
Author

Ah, you are referring to the word "snapshot", I was referring to the LXC snapshot, so I could instantly restore to the previously configured state.

Ah, you are referring to the word "snapshot", I was referring to the LXC snapshot, so I could instantly restore to the previously configured state.
Owner

Which package did you use? Can you provide a link?

Or better yet, what is the exact version string (from the "about" dialogue in the frontend or the vikunja version command on the server) you tested this with?

Which package did you use? Can you provide a link? Or better yet, what is the exact version string (from the "about" dialogue in the frontend or the `vikunja version` command on the server) you tested this with?
Author

Sure, I'll gladly repeat it for you. :-)

About
Frontend Version: 0.22.0
API Version: v0.22.0
root@llama ~ #  vikunja version
Vikunja api version v0.22.0
Built with go1.21.5
Sure, I'll gladly repeat it for you. :-) ``` About Frontend Version: 0.22.0 API Version: v0.22.0 ``` ``` root@llama ~ # vikunja version Vikunja api version v0.22.0 Built with go1.21.5 ```
Owner

Okay, so you tested both times with 0.22 instead of the unstable build one time?

Okay, so you tested both times with 0.22 instead of the unstable build one time?
Author

First time with 0.22, then with unstable and now back to 0.22

We could reproduce the problem everywhere.

First time with 0.22, then with unstable and now back to 0.22 We could reproduce the problem everywhere.
Owner

Which unstable version did you test?

Which unstable version did you test?
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1681
No description provided.