github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-07-16 14:52:35 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #355] Limit check for buckets seems broken #6106

New Issue
Closed
opened 2026-04-20 16:41:14 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-20 16:41:14 -05:00
Owner
Copy Link

Originally created by @Ma27 on GitHub (Nov 13, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/355

Description

I observed it multiple times that even though the amount of cards was well below the limit.
After checking the task_buckets table, I found 201 entries with bucket_id 95 even though said bucket only has 58 entries currently.

After examining the list, I realized that there are also tasks that were

  • closed (even though the saved_filter has done = false)
  • archived projects (my expectation is that these are ignored by filters)
  • stuff that used to have the label that is required to belong to the filter

and probably more.

AFAIU the reason I get the correct amount of cards is because the filter is evaluated each time. If this code would also rely on said table, I'd probably get all 201 entries.

To me this pretty much looks like several write operations don't have an update event for task_buckets.
Also, it would be pretty neat if a migration could clean this table up when the bug gets fixed.

Vikunja Version

0.24.4

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @Ma27 on GitHub (Nov 13, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/355 ### Description I observed it multiple times that even though the amount of cards was well below the limit. After checking the `task_buckets` table, I found 201 entries with `bucket_id` 95 even though said bucket only has 58 entries currently. After examining the list, I realized that there are also tasks that were * closed (even though the saved_filter has `done = false`) * archived projects (my expectation is that these are ignored by filters) * stuff that _used_ to have the label that is required to belong to the filter and probably more. AFAIU the reason I get the correct amount of cards is because the filter is evaluated each time. If this code would also rely on said table, I'd probably get all 201 entries. To me this pretty much looks like several write operations don't have an update event for `task_buckets`. Also, it would be pretty neat if a migration could clean this table up when the bug gets fixed. ### Vikunja Version 0.24.4 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror added the bug label 2026-04-20 16:41:14 -05:00
GiteaMirror commented 2026-04-20 16:41:16 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 15, 2024):

Does this happen only with filters?

<!-- gh-comment-id:2478596836 --> @kolaente commented on GitHub (Nov 15, 2024): Does this happen only with filters?
GiteaMirror commented 2026-04-20 16:41:17 -05:00
Author
Owner
Copy Link

@Ma27 commented on GitHub (Nov 15, 2024):

I only observed it with filters so far, yes.

<!-- gh-comment-id:2478602881 --> @Ma27 commented on GitHub (Nov 15, 2024): I only observed it with filters so far, yes.
GiteaMirror commented 2026-04-20 16:41:18 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 22, 2024):

Does this happen only with bucket filters? I was unable to reproduce this with a saved filter and a manual kanban board.

<!-- gh-comment-id:2493446325 --> @kolaente commented on GitHub (Nov 22, 2024): Does this happen only with bucket filters? I was unable to reproduce this with a saved filter and a manual kanban board.
GiteaMirror commented 2026-04-20 16:41:18 -05:00
Author
Owner
Copy Link

@Ma27 commented on GitHub (Nov 22, 2024):

OK I'll do another reproduction attempt on a fresh installation here soon.

<!-- gh-comment-id:2493578999 --> @Ma27 commented on GitHub (Nov 22, 2024): OK I'll do another reproduction attempt on a fresh installation here soon.
GiteaMirror commented 2026-04-20 16:41:19 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 22, 2024):

A fresh account from https://try.vikunja.io/demo-account-create/ might work as well.

<!-- gh-comment-id:2493596964 --> @kolaente commented on GitHub (Nov 22, 2024): A fresh account from https://try.vikunja.io/demo-account-create/ might work as well.
GiteaMirror commented 2026-04-20 16:41:19 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 19, 2024):

Were you able to reproduce this?

<!-- gh-comment-id:2554683659 --> @kolaente commented on GitHub (Dec 19, 2024): Were you able to reproduce this?
GiteaMirror commented 2026-04-20 16:41:20 -05:00
Author
Owner
Copy Link

@Ma27 commented on GitHub (Dec 19, 2024):

Please give me a few more days, too much other stuff to focus on Vikunja unfortunately :/

<!-- gh-comment-id:2555170759 --> @Ma27 commented on GitHub (Dec 19, 2024): Please give me a few more days, too much other stuff to focus on Vikunja unfortunately :/
GiteaMirror commented 2026-04-20 16:41:21 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 19, 2024):

No worries! Happy to look into this again when you get to it.

<!-- gh-comment-id:2555916147 --> @kolaente commented on GitHub (Dec 19, 2024): No worries! Happy to look into this again when you get to it.
GiteaMirror commented 2026-04-20 16:41:22 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 9, 2025):

Fixed in 1db99dba47, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

<!-- gh-comment-id:2580550990 --> @kolaente commented on GitHub (Jan 9, 2025): Fixed in 1db99dba472974e58a20c0db427880f76d24de9e, please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 16:41:23 -05:00
Author
Owner
Copy Link

@Ma27 commented on GitHub (Jan 12, 2025):

Cannot reproduce anymore, thanks!

<!-- gh-comment-id:2585826828 --> @Ma27 commented on GitHub (Jan 12, 2025): Cannot reproduce anymore, thanks!
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 bug
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#6106
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?