You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, part of the problem for us is that we're including azure-pipeline-go as a dependency, but a substantial majority of our customers aren't actually using it. This ieproxy function syscall is being invoked by the azure-pipeline-go modules at init() time before main is even run: https://github.com/Azure/azure-pipeline-go/blob/master/pipeline/core.go#L202
Would you accept a patch to lazy call newDefaultHTTPClient() the first time you actually need it, rather than at module init() time? This might not solve the problem with the upstream dep, but it would solve our customers issue, given they aren't even using our Azure pipeline functionality.
We've received reports from our users of possible hangs/crashes in go-ieproxy when running on Windows 10. From downstream issue (dapr/cli#707):
We have not been able to reproduce this issue ourselves, but it seems to resemble a known issue in upstream repo: mattn/go-ieproxy#17
The text was updated successfully, but these errors were encountered: