The place to start for issues with areas of Chocolatey that are infrastructure related, or really any issues could be started here. There is also choco for the CLI client, Chocolatey GUI for the GUI.
Apache License 2.0
29
stars
10
forks
source link
Take screenshot of VM desktop on Chocolatey CLI timeout #293
Package Verifier currently takes a screenshot of the test VM's desktop when the overall Vagrant "session" times out.
The resulting gist will include this screenshot and the included logs will abruptly cut off (as they are collected at the time of the Vagrant time out).
It is possible, however, for the Chocolatey CLI command being run to time out before Vagrant. When this happens no screenshot is taken and the logs end "complete" with an exit code.
What is Expected?
A screenshot should be taken and included on the gist if Chocolatey CLI to aid in troubleshooting why the timeout occurred.
How Did You Get This To Happen? (Steps to Reproduce)
It's difficult to force this to happen organically.
It should be possible to reduce the CommandExecutionTimeoutSeconds in package-verifier.exe.config from 2700 to something much lower to force the Chocolatey CLI command to time out before Vagrant (I cannot actually see where the timeout for Vagrant is defined.)
System Details
Operating System: Windows Server 2019
Windows PowerShell Version: 5.1.17763.5202
Chocolatey CLI Version: 0.10.15 (on host)/2.2.2 (inside test environment)
Chocolatey Licensed Extension version: N/A
Chocolatey License type (Professional / Business / ?): N/A
What You Are Seeing?
Package Verifier currently takes a screenshot of the test VM's desktop when the overall Vagrant "session" times out.
The resulting gist will include this screenshot and the included logs will abruptly cut off (as they are collected at the time of the Vagrant time out).
It is possible, however, for the Chocolatey CLI command being run to time out before Vagrant. When this happens no screenshot is taken and the logs end "complete" with an exit code.
What is Expected?
A screenshot should be taken and included on the gist if Chocolatey CLI to aid in troubleshooting why the timeout occurred.
How Did You Get This To Happen? (Steps to Reproduce)
It's difficult to force this to happen organically.
It should be possible to reduce the
CommandExecutionTimeoutSecondsinpackage-verifier.exe.configfrom 2700 to something much lower to force the Chocolatey CLI command to time out before Vagrant (I cannot actually see where the timeout for Vagrant is defined.)System Details
Output Log
Workarounds
N/A
Proposed Solution
Screenshot on Chocolatey CLI timeout (unsure of actual implementation)
Related Issues and Tickets
Done Checklist
┆Issue is synchronized with this Gitlab issue by Unito