I’m having silly lengthy construct times in Windows 11 just recently, as well as I presume it relates to AV.
I’m searching for a main checklist of places that can be contributed to the exemption checklist or directions for just how to effectively omit Go as well as pertinent construct features.
Exists such a checklist someplace?
Hi @sivan, I do not understand about such a checklist, however I would certainly believe that it could be adequate to omit % GOPATH% as well as the present task directory site from AV scanning.
(% GOPATH% consists of the cache for downloaded and install components along with construct artefacts.)
Those still really did not function. Possibly there are various other places, or possibly it’s what Go performs in memory. The only workaround I have actually located is to disable the adhering to in the Windows Safety Facility:
Cloud-Delivered Defense
Automatic example entry
With those handicapped, Go builds quickly once more.
This is intriguing. And also I mean Microsoft does not record what these 2 alternatives do under the hood.
Yet a minimum of you have a workaround.
We can make an enlightened assumption; when you try to run your.go it stops prior to implementation, posts your binary to Microsoft’s web servers where they are checked, awaits authorization, as well as just after that starts implementation. That’s possibly great the very first time you run a brand-new application, however it’s certainly extremely irritating when it’s duplicated whenever you carry out “go build/test/run.”
I believe, given that this is currently made it possible for by default, it could make good sense for the Go neighborhood to think about upgrading the installer and/or paperwork for the Windows variation.
