Ayoub Mrini

Have you checked with @sbdtu5498? As they already have a PR to work on this https://github.com/prometheus/prometheus/pull/12658

> The PR doesn't have the changes for building the image for the arch of current machine, also its been a while since changes have been made to that PR,...

I had a preposition/concern from https://github.com/prometheus/prometheus/pull/12658: > How about > > ``` > .PHONY: docker-current-arch > docker-current-arch: promu > $(PROMU) crossbuild -p linux/$(GOHOSTARCH) > $(MAKE) npm_licenses > $(MAKE) common-docker-$(GOHOSTARCH) >...

I think @SuperQ knows better regarding running `promu crossbuild` on ARM, for me it's meant to run on amd, otherwise it'll spend it's life emulating. In that case, we could...

I still think that adding `promu` as a dep is better than having to run `$(MAKE) $(PROMU)` --- Besides that, I gave this a try on an arm64 ``` $...

Just my 2 cents. Note that if the json formatting isn't required, the series can also be fetched with sth like `promtool tsdb dump | sed 's/} .*/}/' | sort...

Are you able to reproduce this with the latest v3 version? Also sharing more about the build, the OS, the FS would help.

Thanks for the details. Unfortunately, without a reproducer we can’t do much. If you or someone else can work on this, we could emulate a slow disk using something like...

Thanks for the details, having a test that reproduces the issue with what I shared in https://github.com/prometheus/prometheus/issues/16621#issuecomment-2927060022 or at least the steps to reproduce it manually will be really helpful....

Once we reproduce the bug, the ideal fix would be to avoid the SIGSEGV in the first place.