Closed oddcb closed 1 month ago
I just saw this too during local testing, however I am unable to reproduce it again. I tried multiple times, but it does not reoccur.
I suspect this is a bug in the query compilation of the ORM we use, but I'd need a reproducible setup in order to verify.
Put this as p3 for now, as the exception does not have an impact, other than the notification not being sent. If you did not configure an alert for SYSTEM -> DATASOURCE_MIRRORING
, the defect will not affect you at all.
Found the issue and proposed a fix to the ORM project (https://github.com/datanucleus/datanucleus-rdbms/issues/491). This is blocked until the fix is accepted and a new version is released.
Fix was accepted, now waiting for a new DataNucleus release.
Fix was released with DataNucleus 6.0.8.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Current Behavior:
After restarting the api-server it starts updating itself with Github Advisories, OSV etc. After completing the update it crashes:
I have no notifications defined through the UI:
This instance was updated from 4.5.0 to 4.6.0 and then 4.6.1.
PG-version is 14.3-1.pgdg110+1 from postgres:14.3-bullseye@sha256:c976fe9355f53fd93c087e0875be401ad19fa5c3c894b5ae44c03ae9c573cbba
Environment:
Additional Details:
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)