Daniel Demmel

Just to add some more info in case someone else finds this issue, I'm generating the code coverage (using `pytest-cov`) inside a Docker container, so the path is completely different...

OK, another issue, in different repos we have different paths inside Docker (different for a library or a microservice for example), but the array indices are hardcoded so it's only...

Hmm, that fallback to relative sounds perfect, but for me without `remotePathResolve` nothing gets rendered. I can see that the extension is picking up coverage file changes in the output...

Hmm, don't think the issues are related, if I use `remotePathResolve` or set `relative_files = True` everything seems to work perfectly so the Cobertura file itself seems fine. I just...

Oh, one thing which I just realised is that it would probably be useful to link the versions of the Helm chart to the versions of the binary so that...

Hey @wichert, do you think you'll have time to review and comment on this? It's fine if you don't, I can also spin this out into a separate repo, just...

Ah, thanks @frankyhun, I'm using the chart via Helmfile so was just typing the Helm commands into the readme directly 😳 Will update in a minute.

That is because while internally the Kubernetes template and application code is using `SENTRY_DSN` as environment variable, for Helm to be able to template it you need to set the...

I'm really sorry, but I don't think I'll have time in the near future so if anyone has some time to take over, please do!

@wichert it's a single run of the CronJob which was repeated in Sentry, the runs afterwards were successful. It's running in a cluster with 1.16.13-gke.401 This is the template from...