5 ms·
You'd have to maintain multiple projects to do this completely - go tool - gopls - govulncheck That's a lot of effort so you can avoid ~1 report per year?
by verdverm 4y ago
You'd have to maintain multiple projects to do this completely
- go tool
- gopls
- govulncheck
That's a lot of effort so you can avoid ~1 report per year?
> Based on the sample rates, the Go installation might send a report containing the counter values of interest. Typical sample rates would be around 2% (averaging ~1 report per installation per year), but very rare events could be sampled at a higher rate, up to the 10% limit. As more systems take part in transparent telemetry, the overall sample rate on any given system will decrease, because only a fixed number of samples is necessary.
Have you read what they are proposing?