github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-08 04:48:27 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #257] Switching back from :unstable tag to :latest tag breaks website #6016

New Issue
Closed
opened 2026-04-20 16:32:49 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 16:32:49 -05:00
Owner
Copy Link

Originally created by @inuonly on GitHub (Apr 27, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/257

Description

Earlier to test one of the UI issues which was resolves by one of the vikunja team members, we switched from latest tag in docker image to unstable tag
image

Now the change has been added to latest (stable version) so we wanted to switch back. But if change unstable tag to latest, the site breaks following some UI error messages as shown in screenshots below.

We are unable to see any list contents if we click on any list items.
Is there anything else that needs to be taken care of before switching or am I doing this wrong way. Adding some referenc epoint logs.
Steps :

  • when the container is started image
  • few moments later image
  • when we click any list
    image
  • log error after we click any list item in UI
    image

Observations :

  1. This affects overview, upcoming, and any list item, either not loading or loads with same error as above (internal server error) in UI.
  2. However the projects list is still loading. I believe this is only occuring when trying to fetch list items.
  3. We can see in error log that same error is repeating but with different code as shown in following images.
    image
    image
    image

Note:
We are using microsoft todo integration which might be an extra step than standard installation. Ref : #238
This was fixed and was working. So hopefully this does not add overhead to look for error but including this to be on same page for setup.

  • In logs screenshot we have just removed IP address information. Rest is as is.
    Hope this info helps.
    Thanks in advance.

Vikunja Version

v0.23.0+577-fd126fa234

Browser and version

Firefox 125.0.2 (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Viknuja Version :
image

Browser Version :
image

Changes Made :
image

Errors:

  • image
  • image
  • image
  • image
  • image
  • image
Originally created by @inuonly on GitHub (Apr 27, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/257 ### Description Earlier to test one of the UI issues which was resolves by one of the vikunja team members, we switched from latest tag in docker image to unstable tag ![image](https://github.com/go-vikunja/vikunja/assets/26686197/365ba3a1-c688-4a5e-96cd-04deee64424b) Now the change has been added to latest (stable version) so we wanted to switch back. But if change unstable tag to latest, the site breaks following some UI error messages as shown in screenshots below. We are unable to see any list contents if we click on any list items. Is there anything else that needs to be taken care of before switching or am I doing this wrong way. Adding some referenc epoint logs. Steps : - when the container is started ![image](https://github.com/go-vikunja/vikunja/assets/26686197/dd92976c-9939-4cce-92c9-54c5384d5472) - few moments later ![image](https://github.com/go-vikunja/vikunja/assets/26686197/6bb66934-6f3b-4132-9449-cde47b496c73) - when we click any list ![image](https://github.com/go-vikunja/vikunja/assets/26686197/ca6cbcb1-4e9b-463e-a168-92c52dd06f70) - log error after we click any list item in UI ![image](https://github.com/go-vikunja/vikunja/assets/26686197/a24c0759-f309-471c-8161-ee4899cc3025) Observations : 1. This affects overview, upcoming, and any list item, either not loading or loads with same error as above (internal server error) in UI. 2. However the projects list is still loading. I believe this is only occuring when trying to fetch list items. 3. We can see in error log that same error is repeating but with different code as shown in following images. ![image](https://github.com/go-vikunja/vikunja/assets/26686197/eb792b83-f89e-49d6-924d-f7a403107c51) ![image](https://github.com/go-vikunja/vikunja/assets/26686197/e89c5eb0-5076-4184-bdad-e9a5ae90947a) ![image](https://github.com/go-vikunja/vikunja/assets/26686197/211861e4-0bab-4659-92eb-ada224800b5b) Note: We are using microsoft todo integration which might be an extra step than standard installation. Ref : #238 This was fixed and was working. So hopefully this does not add overhead to look for error but including this to be on same page for setup. * In logs screenshot we have just removed IP address information. Rest is as is. Hope this info helps. Thanks in advance. ### Vikunja Version v0.23.0+577-fd126fa234 ### Browser and version Firefox 125.0.2 (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots Viknuja Version : ![image](https://github.com/go-vikunja/vikunja/assets/26686197/03b6cede-2f97-47a1-ac9a-5be2e5723b95) Browser Version : ![image](https://github.com/go-vikunja/vikunja/assets/26686197/e857b561-943d-4a88-8a85-9258914529a7) Changes Made : ![image](https://github.com/go-vikunja/vikunja/assets/26686197/365ba3a1-c688-4a5e-96cd-04deee64424b) Errors: - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/ca6cbcb1-4e9b-463e-a168-92c52dd06f70) - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/7aae6326-82a4-4f8d-8927-05243e715170) - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/a24c0759-f309-471c-8161-ee4899cc3025) - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/eb792b83-f89e-49d6-924d-f7a403107c51) - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/e89c5eb0-5076-4184-bdad-e9a5ae90947a) - ![image](https://github.com/go-vikunja/vikunja/assets/26686197/211861e4-0bab-4659-92eb-ada224800b5b)
GiteaMirror commented 2026-04-20 16:32:51 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 27, 2024):

When did you switch? From 0.23.0 to the version you listed?

<!-- gh-comment-id:2080428671 --> @kolaente commented on GitHub (Apr 27, 2024): When did you switch? From 0.23.0 to the version you listed?
GiteaMirror commented 2026-04-20 16:32:52 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Apr 27, 2024):

today at the time of writing this issue itself. around 2 hours ago.
I took the screenshots by actually changing from unstable to latest in docker compose file then taking screeenshots and then back to unstable as in current state latest tag was unusable for my instance as of now.

<!-- gh-comment-id:2080452178 --> @inuonly commented on GitHub (Apr 27, 2024): today at the time of writing this issue itself. around 2 hours ago. I took the screenshots by actually changing from unstable to latest in docker compose file then taking screeenshots and then back to unstable as in current state latest tag was unusable for my instance as of now.
GiteaMirror commented 2026-04-20 16:32:53 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 28, 2024):

Downgrading is generally not supported. You can only switch to the next stable release or newer unstable builds once you've switched to unstable.
To switch from your unstable installation to a stable version you need to wait for the next release (0.24) and then upgrade from unstable to that.

You have two options now:

  1. Roll back to 0.23.0 and restore from the last backup you have on that version
  2. Stay on unstable until 0.24.0 is released.

If you only want to check things with an unstable build, you should either make the switch generally or make a backup, upgrade to unstable, check whatever you want to check, then go back to the last release and restore from backup.

<!-- gh-comment-id:2081505687 --> @kolaente commented on GitHub (Apr 28, 2024): Downgrading is generally not supported. You can only switch to the next stable release or newer unstable builds once you've switched to unstable. To switch from your unstable installation to a stable version you need to wait for the next release (0.24) and then upgrade from unstable to that. You have two options now: 1. Roll back to 0.23.0 and restore from the last backup you have on that version 2. Stay on unstable until 0.24.0 is released. If you only want to check things with an unstable build, you should either make the switch generally or make a backup, upgrade to unstable, check whatever you want to check, then go back to the last release and restore from backup.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6016
Delete Branch "%!s()"

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?