Paulin Todev

> have you guys been using this code downstream in Agent/Alloy already or would merging this be the first usage of this code? Thank you for the review! This is...

@cstyan thank you so much for the quick and thorough feedback! The problem with the test is that we need to make sure `FileTarget` has already started a `sync`, but...

> The problem with the test is that we need to make sure `FileTarget` has already started a `sync`, but has not yet sent all its data to the channel....

@cstyan No worries, sorry for the late reply - I removed the "continue" comment just now.

> I don't understand why the current behavior is a problem; can you explain more? It is possible to configure an LB exporter with metrics-specific config. This can be done...

Hi @hainenber! Thank you so much, but there are a couple of problems with this task: * It might be a lot of work. Or it might not. I really...

> This is my start up command: @rfratto /bin/prometheus --config.file=/prometheus/prometheus-hash.yml --enable-feature=agent --web.listen-address=:9090 --web.enable-lifecycle --web.enable-admin-api --enable-feature=new-service-discovery-manager --enable-feature=extra-scrape-metrics --enable-feature=expand-external-labels --enable-feature=auto-gomaxprocs Hi @lzfhust, would you mind sharing the contents of the ```/prometheus/prometheus-hash.yml``` file...

I came across this error in a different place. I noticed it in a Grafana Agent, very close to startup time. It was so close to startup time that I...

Below is a summary of my thoughts on this so far. ### A potential workaround In theory this error could happen if the remote write is falling behind. If you...

> Is this a bug? I'd say so. Even if a remote write falls behind, I wouldn't expect it to lose track of the reference ID of a series if...