You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgresErrorException:
🔥
🔥 Postgres ERROR 23503 raised in ri_ReportViolation (ri_triggers.c:2474)
🔥
🔥 Problem: �[36mInsert or update on table "subscription_category_sync_time" violates�[0m
🔥 �[36m foreign key constraint "fk_project".�[0m
🔥 Detail: �[36mKey (project_id)=(44035) is not present in table "project".�[0m
🔥
🔥 The statement under consideration was defined
🔥 at /work/event-log/src/main/scala/io/renku/eventlog/subscriptions/globalcommitsync/LastSyncedDateUpdater.scala:62
🔥
🔥 �[32mINSERT INTO subscription_category_sync_time(project_id, category_name, last_synced)�[0m
🔥 �[32m VALUES ( ($1), $2, ($3))�[0m
🔥 �[32m ON CONFLICT (project_id, category_name)�[0m
🔥 �[32m DO UPDATE SET last_synced = EXCLUDED.last_synced�[0m
🔥
🔥 and the arguments were provided
🔥 at /work/graph-commons/src/main/scala/io/renku/db/SqlStatement.scala:91
🔥
🔥 $1 int4 �[32m44035�[0m
🔥 $2 varchar �[32mGLOBAL_COMMIT_SYNC�[0m
🔥 $3 timestamptz �[32m2022-02-16 09:02:55.542691Z AD�[0m
🔥
🔥 If this is an error you wish to trap and handle in your application, you can do
🔥 so with a SqlState extractor. For example:
🔥
🔥 �[32mdoSomething.recoverWith { case SqlState.ForeignKeyViolation(ex) => ...}�[0m
🔥
skunk.exception.PostgresErrorException: Insert or update on table "subscription_category_sync_time" violates foreign key constraint "fk_project".
at skunk.net.protocol.Execute$$anon$1$$anonfun$$nestedInanonfun$apply$2$1.$anonfun$applyOrElse$8(Execute.scala:69)
at map @ skunk.net.protocol.Execute$$anon$1$$anonfun$$nestedInanonfun$apply$2$1.$anonfun$applyOrElse$8(Execute.scala:63)
at modify @ skunk.util.Pool$.$anonfun$of$2(Pool.scala:91)
at flatten$extension @ skunk.util.Pool$.$anonfun$of$2(Pool.scala:95)
at apply @ skunk.util.Pool$.poolImpl$1(Pool.scala:80)
...
(9 additional frame(s) were not displayed)
GLOBAL_COMMIT_SYNC: finding events to dispatch failed
The text was updated successfully, but these errors were encountered:
Sentry Issue: RENKU-GRAPH-N
The text was updated successfully, but these errors were encountered: