3 ms·
Still, opt-out is just inacceptable. At least with a mechanism which can easily fail, like setting an environment variable. This basically forces you to wrap th
by _ph_ 4y ago
Still, opt-out is just inacceptable. At least with a mechanism which can easily fail, like setting an environment variable. This basically forces you to wrap the go tool in a script which ensures the environment variable to be set.
As this seem to cache the results, another option is to fiddle with the cache to report bogus information.
- Thaxll 4y agoYou can set env variable for the go toolchain with a command such as: go env -w TELEMETRY=off which will be written to disk and use by the go cli.
- _ph_ 4y agoWhere will it be written to and how is it guaranteed to be picked up by any further invocations of the tools?
- JetSpiegel 4y agoWhat if a new version of go uses TELEMETRY_ENABLED? Do you read all the changelogs, always?
- simoncion 4y agoYeah, given go's history with breaking changes (and the habit of OKR-chasing managers and Senior Staff to make Number Go Up to look good on the promo packet), I definitely would not trust any opt-out mechanism to not receive operationally-significant changes in the next five years.
- Thaxll 4y agoAs far as I known go never changed any flags since release ( 2012 ), is it good enough for you?
- deleted 4y ago[deleted]