hadi javeed
hadi javeed
Node version 5.4.1 Webpack Chromium (Google Chrome Linux Version)
@onlyann thank you for your reply. how can I run a loop to catch these errors? Database connection is available, I was able to validate other Psycog library connections, not...
so I added the loop and re-try mechanism, but seems like following SQL error breaks the full flow ```txt db | 2024-07-10 18:00:31.609 UTC [37] STATEMENT: SELECT id, status, task_name,...
@medihack I am using 2.7.0 version, since I did not lock the package version and yes it's very frustrating whole worker would crash again and again due to missing column...
I am unsure if this is related to the new package release 2.7.0, but the worker crashed repeatedly on a small SQL exception. and the error log produced by procrastinate...
thank you for the help. and makes sense. I think for now locking a version would help still unclear on why the worker crashes every time on small minor errors...
@medihack I have upgraded the package, it has fixed the schema inconsistency error but I still run into the following error consistently from time to time, even re-starting the worker...