(Unstable) API panic since last update #138

@fma965 commented on GitHub (May 28, 2023):

Same here, had to revert to 0.20.4

@fma965 commented on GitHub (May 28, 2023): Same here, had to revert to 0.20.4

GiteaMirror commented

@kolaente commented on GitHub (May 30, 2023):

@Break-Off Can you run the following query in your database and post the results?

select *
from team_namespaces
where namespace_id not in (select id from namespaces);

@kolaente commented on GitHub (May 30, 2023): @Break-Off Can you run the following query in your database and post the results? ```sql select * from team_namespaces where namespace_id not in (select id from namespaces);

GiteaMirror commented

@Break-Off commented on GitHub (May 31, 2023):

@kolaente Here is the command output:

MariaDB [VK_database]> select * from team_namespaces where namespace_id not in (select id from namespaces);
+----+---------+--------------+-------+---------------------+---------------------+
| id | team_id | namespace_id | right | created             | updated             |
+----+---------+--------------+-------+---------------------+---------------------+
|  1 |       2 |            8 |     1 | 2022-08-25 16:25:22 | 2022-08-25 16:25:25 |
+----+---------+--------------+-------+---------------------+---------------------+
1 row in set (0.004 sec)

Thanks.

@Break-Off commented on GitHub (May 31, 2023): @kolaente Here is the command output: ``` MariaDB [VK_database]> select * from team_namespaces where namespace_id not in (select id from namespaces); +----+---------+--------------+-------+---------------------+---------------------+ | id | team_id | namespace_id | right | created | updated | +----+---------+--------------+-------+---------------------+---------------------+ | 1 | 2 | 8 | 1 | 2022-08-25 16:25:22 | 2022-08-25 16:25:25 | +----+---------+--------------+-------+---------------------+---------------------+ 1 row in set (0.004 sec) ``` Thanks.

GiteaMirror commented

2025-11-01 20:48:26 -05:00

@kolaente commented on GitHub (May 31, 2023):

Can you delete that entry and try again?

@kolaente commented on GitHub (May 31, 2023): Can you delete that entry and try again?

GiteaMirror commented

@Break-Off commented on GitHub (May 31, 2023):

Can you delete that entry and try again?

It works now, but the DB is now a mess, at least looking at it from the frontend. All my projects have vanished except nine of them which have duplicated six times, tasks done from a while ago are now undone, and all the tasks don't have a parent project (they only show on the overview).

@Break-Off commented on GitHub (May 31, 2023): > Can you delete that entry and try again? It works now, but the DB is now a mess, at least looking at it from the frontend. All my projects have vanished except nine of them which have duplicated six times, tasks done from a while ago are now undone, and all the tasks don't have a parent project (they only show on the overview). ![image](https://github.com/go-vikunja/api/assets/5843433/4d55d7ff-7c3f-439b-bf94-028d9ecae6e4)

GiteaMirror commented

2025-11-01 20:48:26 -05:00

@Break-Off commented on GitHub (Jun 1, 2023):

Hey, I've made a partial dump of the projects table of my DB and it seems that the repeated projects are part of the migration of the offending build:

It goes up to 62900 rows (!)

@Break-Off commented on GitHub (Jun 1, 2023): Hey, I've made a partial dump of the projects table of my DB and it seems that the repeated projects are part of the migration of the offending build: ![image](https://github.com/go-vikunja/api/assets/5843433/f692ba70-40e7-49c7-aa1f-579853ad7da9) It goes up to 62900 rows (!)

GiteaMirror commented

2025-11-01 20:48:26 -05:00

@kolaente commented on GitHub (Jun 6, 2023):

Well, that should not happen.

I tried to reproduce this with a prod dump of my own instance, but it did not duplicate any projects. The migration only created new projects for old namespaces, as it should.

Are the duplicated projects ones which were created for old namespaces, or are they projects which existed before the migration?

I noticed a few little things which caused archived subprojects to show up again, and minor ui issues. Also a bug which caused some subprojects to be unavailable. These should now be fixed. Please update once the build is done again to see if you can now see all projects.

and all the tasks don't have a parent project (they only show on the overview).

Can you check in the db which project these tasks belong to?

@kolaente commented on GitHub (Jun 6, 2023): Well, that should not happen. I tried to reproduce this with a prod dump of my own instance, but it did not duplicate any projects. The migration only created new projects for old namespaces, as it should. Are the duplicated projects ones which were created for old namespaces, or are they projects which existed before the migration? I noticed a few little things which caused archived subprojects to show up again, and minor ui issues. Also a bug which caused some subprojects to be unavailable. These should now be fixed. Please update [once the build is done](https://drone.kolaente.de/vikunja/api/5178) again to see if you can now see all projects. > and all the tasks don't have a parent project (they only show on the overview). Can you check in the db which project these tasks belong to?

GiteaMirror commented

@variasdesign commented on GitHub (Jun 7, 2023):

EDIT: This is another account of mine. I'm @Break-Off

Are the duplicated projects ones which were created for old namespaces, or are they projects which existed before the migration?

The first: old namespaces turned to projects.

I noticed a few little things which caused archived subprojects to show up again, and minor ui issues. Also a bug which caused some subprojects to be unavailable. These should now be fixed. Please update once the build is done again to see if you can now see all projects.

Yes, I've got these bugs too, particularly the hidden subprojects. Although I've already moved them out of the hidden parent project and remade it.

and all the tasks don't have a parent project (they only show on the overview).

Can you check in the db which project these tasks belong to?

They belong to the hidden subprojects.

Thanks for your work!

@variasdesign commented on GitHub (Jun 7, 2023): EDIT: This is another account of mine. I'm @Break-Off > Are the duplicated projects ones which were created for old namespaces, or are they projects which existed before the migration? The first: old namespaces turned to projects. > I noticed a few little things which caused archived subprojects to show up again, and minor ui issues. Also a bug which caused some subprojects to be unavailable. These should now be fixed. Please update [once the build is done](https://drone.kolaente.de/vikunja/api/5178) again to see if you can now see all projects. Yes, I've got these bugs too, particularly the hidden subprojects. Although I've already moved them out of the hidden parent project and remade it. > > and all the tasks don't have a parent project (they only show on the overview). > > Can you check in the db which project these tasks belong to? They belong to the hidden subprojects. Thanks for your work!

GiteaMirror commented

@kolaente commented on GitHub (Jun 7, 2023):

The first: old namespaces turned to projects.

Where they all created at once or did you run the migration multiple times? Or put the other way, if you restore an old dump from before running the migration and upgrade from there, do you get duplicate projects again?

@kolaente commented on GitHub (Jun 7, 2023): > The first: old namespaces turned to projects. Where they all created at once or did you run the migration multiple times? Or put the other way, if you restore an old dump from before running the migration and upgrade from there, do you get duplicate projects again?

GiteaMirror commented

@fma965 commented on GitHub (Jun 29, 2023):

I'm not sure if you fixed this or i did by cleaning up some random entries in my SQL but it's now working for me on "latest"

@fma965 commented on GitHub (Jun 29, 2023): I'm not sure if you fixed this or i did by cleaning up some random entries in my SQL but it's now working for me on "latest"

GiteaMirror commented

@kolaente commented on GitHub (Jun 29, 2023):

@Fma965 latest or unstable? latest is the last release.

@kolaente commented on GitHub (Jun 29, 2023): @Fma965 latest or unstable? latest is the last release.

GiteaMirror commented

@fma965 commented on GitHub (Jun 29, 2023):

Frontend Version: 0.20.5
API Version: v0.20.4

@fma965 commented on GitHub (Jun 29, 2023): Frontend Version: 0.20.5 API Version: v0.20.4

GiteaMirror commented

@kolaente commented on GitHub (Jun 30, 2023):

The last release does not have the changes causing the issue.

@kolaente commented on GitHub (Jun 30, 2023): The last release does not have the changes causing the issue.

GiteaMirror commented

@variasdesign commented on GitHub (Jun 30, 2023):

The first: old namespaces turned to projects.

Where they all created at once or did you run the migration multiple times? Or put the other way, if you restore an old dump from before running the migration and upgrade from there, do you get duplicate projects again?

Sorry for my lack of response. I've tried to recreate the old dump in unstable but for some reason my MariaDB container didn't want to start and I parked it. I purged the offending namespaces/projects and all is working correctly now. Alas, that doesn't help you much, sorry about that. Also, yes, I'm guessing the migration ran multiple times since I recreated the container repeatedly.

@variasdesign commented on GitHub (Jun 30, 2023): > > The first: old namespaces turned to projects. > > Where they all created at once or did you run the migration multiple times? Or put the other way, if you restore an old dump from before running the migration and upgrade from there, do you get duplicate projects again? Sorry for my lack of response. I've tried to recreate the old dump in unstable but for some reason my MariaDB container didn't want to start and I parked it. I purged the offending namespaces/projects and all is working correctly now. Alas, that doesn't help you much, sorry about that. Also, yes, I'm guessing the migration ran multiple times since I recreated the container repeatedly.

GiteaMirror commented