commit | 0b706e19b70189f217f242e6875dc0bb8e64b601 | [log] [tgz] |
---|---|---|
author | Rob Findley <rfindley@google.com> | Wed Jul 17 17:40:07 2024 +0000 |
committer | Gopher Robot <gobot@golang.org> | Wed Jul 17 19:47:52 2024 +0000 |
tree | 2c4654d65dcee49b2eebc8c0218a4d79a27651ee | |
parent | d2ee678ccaf8b11efd921ef369c5863e20be8506 [diff] |
counter: avoid the rotation timer in counter.Open As observed in golang/go#68497, scheduling a rotation timer can break runtime deadlock detection (all goroutines are asleep...). Furthermore, for short-lived processes such as command line tools, there is no reason to schedule a file rotation. Therefore, change the default behavior of counter.Open not to rotate the counter file, and introduce a new OpenAndRotate API to be used by gopls. For golang/go#68497 Change-Id: I7929c2d622d15e36ca99036d8c7eac1eed8fabf5 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/599075 Auto-Submit: Robert Findley <rfindley@google.com> Reviewed-by: Michael Matloob <matloob@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This repository holds the Go Telemetry server code and libraries, used for hosting telemetry.go.dev and instrumenting Go toolchain programs with opt-in telemetry.
Warning: this repository is intended for use only in tools maintained by the Go team, including tools in the Go distribution and auxiliary tools like gopls or govulncheck. There are no compatibility guarantees for any of the packages here: public APIs will change in breaking ways as the telemetry integration is refined.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the time repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/telemetry:” in the subject line, so it is easy to find.
This repository uses eslint to format TS files, stylelint to format CSS files, and prettier to format TS, CSS, Markdown, and YAML files.
See the style guides:
It is encouraged that all TS and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install
./npm run all