Markus Dobel
Markus Dobel
The action is quite specific on Linux and depends on the concrete VM types and available mounts -- it also abuses the fact, that the disks (amount and sizes) are...
Some additional points I found: Prometheus does not detect the counter as such, but I have no idea why. When using the Prometheus Web UI (to rule out Grafana as...
Not an actual solution, but another workaround: instead of using default arguments, implement the telescoping methods explicitly. These can then be mocked individually, and work as expected. ```kotlin class OfferService(private...
I can confirm -- the same issue is there with 5.8.0
Not as large as in other projects, but I can notice a slowdown in https://github.com/easimon/tado-exporter as well (which severely suffers coverage / does not have a lot of tests). With...
When setting `kotest.framework.discovery.jar.scan.disable=true`, kotest fails to instanciate the `AuthClientIntegrationTest`, with both kotest 5.6.2 and kotest 5.8.0, because of a missing no-arg-constructor. So the setting seems to have an effect prior...
Sorry for all the questions -- but then I think I still don't understand: - With kotest 5.6.2 and no additional kotest.properties configuration or ProjectConfig, the tests started quickly, and...
Following are a few samples around one "missed" reset: At this time, the corresponding plug was unplugged and re-plugged after a short time, resetting the internal counter. ``` 20289.366666666665 @1665081057.602...
It seems my assumption on "`NaN` being fine" was wrong, and the result of prometheus aggregations over intervals with `NaN`s is somewhat unpredictable. I am unsure why these `NaN` values...
Issue can be closed, since it was a user / data error. Since I made sure that the time series does not contain `NaN`, all aggregation functions work as expected.