Tidhar Klein Orbach

@eriwen can you please give an example how to use the NodeTask?

I also see this issue: > time="2018-08-06T05:05:48.591754629Z" level=error msg="Error running exec 673c1fc689e85c542d12188b7bec2819638bfedb9c05b894c072d1c6d5f5a7d2 in container: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused \"process_linux.go:86: executing setns process caused...

@GiedriusS I'm using a specific timestamp. for me it reproduces any time on my environment. it's a counter metric that comes from 2 prometheus replicas. @MichaHoffmann I tried to debug...

found something interesting, if I do ``` my_metric{_label_0="service",_label_1="requests",_label_2="timer", server="server00102"}[5m] ``` without deduplication in a specific timestamp I get the following: server1: ``` 2583033 @1714665427.092 2588869 @1714665487.092 2594666 @1714665547.092 2600461 @1714665607.092...

I managed to reproduce this use case in a unit test. I added the following test case to [TestDedupSeriesSet](https://github.com/thanos-io/thanos/blob/main/pkg/dedup/iter_test.go#L273) in **dedup/iter_test.go**: ``` { name: "My Regression test", isCounter: true, input:...

perhaps I'm mixing, but shouldn't --query.default-step affect that penalty? also, I might be able with a PR once there will be a design for the fix.

hi @MichaHoffmann @GiedriusS @fpetkovski @yeya24 I added a PR with a suggested fix, can you please check and let me know what do you think? thanks!