Comparing changes
Open a pull request
- 12 commits
- 25 files changed
- 8 contributors
Commits on Mar 18, 2025
-
Update common Prometheus files (#671)
Signed-off-by: prombot <prometheus-team@googlegroups.com>
Update common Prometheus files (#709)
Signed-off-by: prombot <prometheus-team@googlegroups.com>
Commits on Mar 23, 2025
-
Update common Prometheus files (#710)
Signed-off-by: prombot <prometheus-team@googlegroups.com>
Commits on Mar 31, 2025
-
* Update latest Go to 1.24. * Update minimum Go to 1.23. * Bump Go modules. Signed-off-by: SuperQ <superq@gmail.com>
-
Update common Prometheus files (#713)
Signed-off-by: prombot <prometheus-team@googlegroups.com>
Commits on Apr 19, 2025
-
chore: Upgrade golangci-lint to v2 (#715)
- Migrate the configuration file - Update the tooling version and CI - Apply auto-fixes Signed-off-by: Kemal Akkoyun <kemal.akkoyun@datadoghq.com>
-
Use SysReadFile for thermals and skip failed zones (#712)
Switches all calls in the thermal zones processing to use SysReadFile so that unavailable zones won't stall forever waiting for them to become available. Also continues processing in the case that one zone fails with EAGAIN, as is the case for temporarily unavailable zones. Addresses #698 Signed-off-by: Sean Swehla <sean@sweh.la>
-
class_infiniband: continue on syscall EINVAL (#705)
#704 In some very bleeding-edge configurations, syscalls against some IB counters will return `invalid argument`. This bubbles back to callers (e.g. node_exporter) in a very bad way -- e.g. all IB metrics collection failing when a single or group of IB ports returns this. Suspect this has always been an error case and possible to experience, but it's the first time we're seeing it in a very new hardware deployment. Signed-off-by: Michael Fuller <mfuller@lambdal.com>
-
build(deps): bump golang.org/x/sys from 0.31.0 to 0.32.0 (#717)
Bumps [golang.org/x/sys](https://github.com/golang/sys) from 0.31.0 to 0.32.0. - [Commits](golang/sys@v0.31.0...v0.32.0) --- updated-dependencies: - dependency-name: golang.org/x/sys dependency-version: 0.32.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
Update class_infiniband.go (#687)
Signed-off-by: Jeffrey Chu <oneoneonepig@users.noreply.github.com>
-
build(deps): bump golang.org/x/sync from 0.12.0 to 0.13.0 (#716)
Bumps [golang.org/x/sync](https://github.com/golang/sync) from 0.12.0 to 0.13.0. - [Commits](golang/sync@v0.12.0...v0.13.0) --- updated-dependencies: - dependency-name: golang.org/x/sync dependency-version: 0.13.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
infiniband: do not make assumptions about counters based on HCA name (#…
…678) Some users have reported cases of systemd "predictable network interface naming" apparently also renaming the HCA device. This means we can no longer make assumptions about which counter(s) should be present based on the HCA name (i.e., irdma*, mlx5_*). The previous approach was quite brittle anyway, since there will undoubtedly be other IB / RoCE drivers in future which implement the hw_counters directory (but not the older counters directory). Signed-off-by: Daniel Swarbrick <daniel.swarbrick@gmail.com> Signed-off-by: Ben Kochie <superq@gmail.com> Co-authored-by: Ben Kochie <superq@gmail.com>
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.16.0...v0.16.1