Open
Conversation
Owner
|
Hi, yep this was brought up in #65. A long time ago I opened an issue about this in Rails at rails/rails#52558 too. Deleting the old pid before Puma boots feels like probably the safest bet since the pid will exist once the container starts which will handle the LSP case or whatever else. I do wonder about the env var approach though. |
Contributor
Author
|
Oh neat, yeah I agree... it does look like that env var to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I believe this might make the repo a little more resilient to (my) bad improper container shutdown habits, would you accept this upstream?