Repository navigation
Conversation
If a process is replaced by a project update (e.g. POST /project/configuration) while it is restarting, the update starts a new instance and the restart starts another one when its backoff ends. The second overwrites the first in runningProcesses, so the first keeps running but can no longer be listed or stopped, and it outlives process-compose. Removing or replacing a process now counts as a stop request, so the pending restart is dropped. As a fallback, addRunningProcess stops a still-running instance that it replaces.
|
Author
|
Sounds related to #570 |
This branch has not been deployed
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
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.
While working on different projects I recognnized an annoying pattern. Sometimes my devenv shell would rebuild after a code change and then the process manager would get confused all over the place. I thought it's my local steup but it turns out that there is an issue when changes come in too quickly