Skip to content
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

Exception doesn't bubble up: instead, it's swallowed and prevents container from restarting #781

Open
ffissore opened this issue Feb 1, 2024 · 0 comments

Comments

@ffissore
Copy link

ffissore commented Feb 1, 2024

Hi all. As per the subject, we use dependency injector in one of our services.
Part of the setup phase is to connect to the database and initialise all the prepared statements.
In CI, the database takes some time to get up and running, so some statements fail to be prepared.
This is an expected situation and we rely on the exception bubbling up and causing the process to terminate, and be restarted by docker compose.

However, this does happen. The exception is logged, but the process doesn't terminate.

We tried a handful of times to create a Minimum, Reproducible Example, but we failed. Maybe some have seen and found the cause or a workaround for this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant