Abdul Salama

02/22/2023, 8:55 PM
Hi folks, we keep getting this error pop up at the dagit UI. It is a benign error that we usually just close out and it doesn't cause any problems. But it is annoying and was wondering if anyone has any hints why it happens:
Operation name: LastTenRunsPerJobQuery

Message: (psycopg2.OperationalError) server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.

[SQL: SELECT event_logs.dagster_event_type, count(*) AS n_events_of_type, max(event_logs.timestamp) AS last_event_timestamp 
FROM event_logs 
WHERE event_logs.run_id = %(run_id_1)s AND event_logs.dagster_event_type IS NOT NULL GROUP BY event_logs.dagster_event_type]
[parameters: {'run_id_1': '1faa7aaa-09ce-4736-b3f6-52a68e76b8c3'}]
(Background on this error at: <>)

Path: ["workspaceOrError","locationEntries",0,"locationOrLoadError","repositories",0,"pipelines",0,"runs",0,"startTime"]

Locations: [{"line":55,"column":3}]


02/22/2023, 10:09 PM
Hi Abdul. There were some issues with a recent release of psycopg2 that were incompatible with dagster. have you upgraded to the latest version of dagster? if so, or if you upgrade and see the same issue, let me know so i can pass it on to the team