Daniel Swarbrick

See https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/pull/20

Isn't this somewhat redundant, given that there are already two SMART collectors in this repo, which are capable of fetching HDD temperatures (and much more)?

Also just ran into this. As a workaround (since I don't need Jupyter support), I simply disabled the Jupyter extension. Now I can see my code again, instead of a...

This sounds like basically the same issue as #8661, and is likely to occur on any 32-bit arch, i.e. if processes are limited to 4 GiB memory or less. IIRC,...

FWIW, I'm not able to get the `TestRulesUnitTest/Long_evaluation_interval` test to fail in a resource-constrained systemd slice with `GOARCH=386`, e.g.: ``` $ systemd-run --scope -p MemoryMax=1G -p MemorySwapMax=0 -E GOARCH=386 go...

> Or depend on https://github.com/beorn7/floats :o) I would prefer not to have to package yet another tiny dependency to make this build on Debian (and derivatives), so I would advocate...

I presume that this test will need special handling for Go 1.17 / 1.18, and 1.19, as per the prometheus/go_collector_metrics_go1{17,18,19}_test.go files. Specifically, Go 1.19 seems to expose four additional metrics:...

> work fine with me on go1.18.6. some fail on 1.19. See my second comment. Updated title to avoid confusion.

Does Circle CI support testing on 32-bit arch? If so, and it is enabled in the config, that would catch such oversights in future. Alternatively, add a test on amd64...

When this is merged, it would be nice to also update the circleci config to actually _test_ with Go 1.19 (as the release notes state).