-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Adding new projects fail due to an Django IntegrityError in v2025.12 #402
Comments
Hi, Downgrading the database schema is quite tricky. Here are the steps:
What exactly is the bug why you downgraded in the first place? |
The bug I presented was the reason why we "downgraded". I should have made this more clear: Timeline: |
Ok. Thanks for the info. I could not reproduce the database error locally. I found no (obvious) place in the source code where |
How and where do we can get the required stack-trace?
Edit: Here's the payload too. I figured it would be helpful to see what goes into the system.
|
You can get the stack trace of the SysReptor backend via The payload looks fine. However, the JavaScript stacktrace is strange. It contains wrong line numbers and a reference to The caching problem, however, does not explain the |
|
Thank you. It seems that there is indeed an older version of the SysReptor docker image running. The line numbers from the django stacktrace do not fit the current version, but an older one released some months ago. I guess the update script downloaded the new SysReptor docker image and applied the database migrations, but then somehow did not start the new image. We will investigate why this is the case. As a quick workaround you can force pull |
That did it actually. Thanks for the help so far. We are now on 2025.12 and the error is gone. |
I think this error was caused by an error while bringing up the docker containers. It might also happen if the update script is cancelled using Ctrl+C while the containers are starting. In this line, we try to bring up the containers. The containers start and migrations of the new SysReptor version are applied. Recreating your docker containers might have worked because in the update script, we set the environment variable I'm not quite sure, why your last output says Anyway, I suggest to remove the instruction to restore the previous version here. This would mean that if bringing up the docker containers fail, they can still be brought up manually (even if migrations were already applied). |
…o 'main' Remove error_cleanup to not roll back version after migrations were applied See merge request reportcreator/reportcreator!865
The newest version (2025.12) of Sysreptor has a potential bug, that caused us to revert the update to 2025.4.
The error occurs when creating a new project or importing a report template. This is probably because the same API endpoint is used for both operations.
In both cases we get errors like these:
Other operations like adding findings to an existing project works as expected.
The text was updated successfully, but these errors were encountered: