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

fix: specify max named pipe instances #86

Merged
merged 1 commit into from
Mar 15, 2024
Merged

Conversation

Honglichenn
Copy link
Contributor

@Honglichenn Honglichenn commented Mar 15, 2024

What was the problem/requirement? (What/Why)

In previous implementation, the max named pipe instances is not limited, which may run out of the resources.

What was the solution? (How)

Restrict the max number of the named pipe instances to avoid this risk.

What is the impact of this change?

Make the code safer.

How was this change tested?

All existing tests are passed.

Was this change documented?

N/A

Is this a breaking change?

N/A


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Honglichenn Honglichenn marked this pull request as ready for review March 15, 2024 16:33
@Honglichenn Honglichenn requested a review from a team as a code owner March 15, 2024 16:33
@jusiskin jusiskin changed the title chore: Change max named pipe instances number fix: specify max named pipe instances Mar 15, 2024
@jusiskin jusiskin added bug Something isn't working security Pull requests that could impact security labels Mar 15, 2024
@jusiskin jusiskin merged commit d959381 into mainline Mar 15, 2024
12 checks passed
@jusiskin jusiskin deleted the honglich/namedpipe_num branch March 15, 2024 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working security Pull requests that could impact security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants