-
Notifications
You must be signed in to change notification settings - Fork 195
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
backend: Prevent flashing terminal on Windows #2756
Conversation
daf3890
to
2080422
Compare
2080422
to
857c4fe
Compare
Backend Code coverage changed from 63.8% to 59.9%. Change: -3.9% 😞. Coverage report
|
857c4fe
to
0655313
Compare
Backend Code coverage changed from 63.8% to 59.9%. Change: -3.9% 😞. Coverage report
|
I will try to add the exec_test.go from upstream. |
0655313
to
608f139
Compare
Backend Code coverage changed from 63.8% to 64.9%. Change: 1.1% 😃. Coverage report
|
Tested using Azure AKS cluster with Entra ID that executes azure-cli kubeconfig
Can confirm that it doesn't open terminal windows anymore. |
608f139
to
e1268cf
Compare
Backend Code coverage changed from 63.8% to 64.9%. Change: 1.1% 😃. Coverage report
|
On Windows, even when the exec plugin's command is not interactive, running the command was still making the terminal window flash (default behavior on Windows). This can be annoying if a tool runs the exec plugin frequently. This patch prevents that problem by setting a sys proc attribute to hide windows, only when in the Windows platform and when the exec is non-interactive. Signed-off-by: Joaquim Rocha <joaquim.rocha@microsoft.com>
e1268cf
to
125697b
Compare
Backend Code coverage changed from 63.8% to 64.9%. Change: 1.1% 😃. Coverage report
|
On Windows, even when the exec plugin's command is not interactive, running the command was still making the terminal window flash (default behavior on Windows). This can be annoying if a tool runs the exec plugin frequently. This patch prevents that problem by setting a sys proc attribute to hide windows, only when in the Windows platform and when the exec is non-interactive.
How to test:
On Windows:
CreateEmptyFile.cmd
script in your home folder:On non-Windows:
fixes #2346