Closed spkamboj closed 2 months ago
I assume you have tested this with DCM?
Yes, I tested it with DCM on all three platforms.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
What was the problem/requirement? (What/Why)
When using deadline auth login and deadline gui for login using Deadline Cloud monitor, there is race condition that Deadline Cloud monitor process handle closes early while the application is starting. This closes the stderr pipe opened with Deadline Cloud monitor process, and any messages sent to stderr results in panic, crashing the Deadline Cloud monitor.
What was the solution? (How)
The error messages in stderr are coming from crates used in DCM, which login flow does not need to know. DCM itself sends login failure message over stdout. This change is pointing process stderr pipe to devnull to prevent panic.
What is the impact of this change?
Fix the race condition which crashes the Deadline Cloud monitor application during login.
How was this change tested?
Was this change documented?
Not applicable, no APIs or customer behaviors are changed.
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.