After the update of containter to rc3.
This error message is appeared:
Migration failed: migration 20251001113831 failed: json: cannot unmarshal object into Go struct field bucketConfigurationCatchup.filter of type string
The container doesn’t start anymore.
I have reverted to rc2
Which database are you using?
Can you run this sql in your database and post the result? (redact any personal information)
SELECT * from project_views WHERE bucket_configuration_mode = 2 AND bucket_configuration::text like '%\"filter\":\"%' AND bucket_configuration::text not like '%\"filter\":{\"filter\":%'
56 Mxxx 6 3 {"s":"","sort_by":null,"order_by":null,"filter":"assignees in mxxx@xxxx.com","filter_include_nulls":false} 62.5 2 [{"title":"To-do","filter":{"s":"","sort_by":null,"order_by":null,"filter":"labels in 23","filter_include_nulls":false}},{"title":"Doing","filter":{"s":"","sort_by":null,"order_by":null,"filter":"labels in 24","filter_include_nulls":false}},{"title":"Done","filter":{"s":"","sort_by":null,"order_by":null,"filter":"labels in 15","filter_include_nulls":false}}] 0 0 2025-11-26 14:18:14.000 2025-11-26 14:18:08.000
Have you find something? @kolaente
Can I try again to migrate?
@kolaente Any idea to solve migration issue??
I’m working on a solution here: fix: handle mixed-format bucket configurations in migration by kolaente · Pull Request #2033 · go-vikunja/vikunja · GitHub
Many thanks for your feedback.
If you want, I can validate the patch when it will be ready.
The fix is now merged and released in unstable builds, please check.
Ok thanks. Monday, I tried but it was not working.Next week I will test again.
Like before the problem is not solved:
2026-Jan-12 08:15:56
time=2026-01-12T09:15:56.381+01:00 level=ERROR msg="Migration failed: migration 20251001113831 failed: json: cannot unmarshal object into Go struct field bucketConfigurationCatchup.filter of type string"
Which version are you using? (fron the vikunja version command or the log message that’s printed on start)
I have migrated rc4 without no difficultés but this bug is fixed.
Many thanks.