-
Notifications
You must be signed in to change notification settings - Fork 85
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
Limit Daemon Concurrency on Windows #1322
Conversation
Signed-off-by: Andrew W. Harn <andrew.harn@broadcom.com>
Signed-off-by: Timothy Johnson <timothy.johnson@broadcom.com>
Signed-off-by: Andrew W. Harn <andrew.harn@broadcom.com>
Signed-off-by: Andrew W. Harn <andrew.harn@broadcom.com>
Codecov Report
@@ Coverage Diff @@
## next #1322 +/- ##
==========================================
+ Coverage 91.39% 91.49% +0.09%
==========================================
Files 369 369
Lines 5752 5748 -4
Branches 826 824 -2
==========================================
+ Hits 5257 5259 +2
+ Misses 489 483 -6
Partials 6 6
Continue to review full report at Codecov.
|
Signed-off-by: Andrew W. Harn <andrew.harn@broadcom.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for also fixing the is_daemon_running
check 🙂
Signed-off-by: Andrew W. Harn <andrew.harn@broadcom.com>
0fed8dd
Kudos, SonarCloud Quality Gate passed! |
Due to the implementation of named pipes in Windows, it is not possible to determine if another daemon client is talking to the daemon server using the named pipes alone. Instead, this PR introduces a 'lock file' that is locked when a client is communicating with the server, and released when the client is finished. The lock file's location can be overridden with the ZOWE_DAEMON_LOCK environment variable.