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.

Sign up for GitHub

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

Jump to bottom

Starting a service starved for resources can happen while proxy is stopping #10

Open
perk11 opened this issue Sep 20, 2024 · 1 comment
Open

Starting a service starved for resources can happen while proxy is stopping #10

perk11 opened this issue Sep 20, 2024 · 1 comment

Comments

@perk11
Copy link
Owner

perk11 commented Sep 20, 2024

After interrupt signal is received, a service that previously had no resources to start can get started after resources are freed by the interrupt command.

The proxy should instead close connections for services that hasn't yet started
perk11 added a commit that referenced this issue Sep 23, 2024
@perk11
Add exit points when program was interrupted to functions locking the…
b67f4b0 
… service mutex

Fix #14 and potentially #10
@perk11
Copy link
Owner Author

perk11 commented Sep 23, 2024

This should be fixed in b67f4b0, but I will keep this open until there is a test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@perk11