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

feat: Add max_restarts to all services to avoid restarting indefinitely #311

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

shivaraj-bh
Copy link
Member

resolves #309

@shivaraj-bh shivaraj-bh merged commit e88a852 into main Sep 4, 2024
2 checks passed
@shivaraj-bh shivaraj-bh deleted the max-restarts branch September 4, 2024 11:30
Copy link
Member

@srid srid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wasn't this used to be the case before? I vaguely remember process restarts never being infinite to begin with (I've seen processes enter into 'exited' state in process-compose window).

In any case, this change only affects services. Should we make it a default in process-compose-flake? Actually why not make it a default in process-compose itself?

Incidentally, there's no guarantee that a new service added to the repo will follow the same max_restarts convention. It is easy to miss that, so we should think about solving this more fundamentally.

@srid srid mentioned this pull request Sep 7, 2024
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

Successfully merging this pull request may close these issues.

postgres: Don't infinitely keep restarting when DB couldn't start
2 participants