Steven Sklar

@bassplay3r, following up on this issue, have you been able to resolve it? Since this is stale, I would recommend retrying using a more recent chart release.

@stalek71 , when I `curl -IL https://questdb.github.io/questdb-kubernetes/questdb-0.20.8.tgz`, I get a 301 -> 200 HTTP response. Can you please copy the command you're running (along with your local `helm` version number)...

closed by https://github.com/questdb/questdb/pull/2737

@bluestreak01 here's an update on this. I just merged master into this branch, fixed merge conflicts, and all tests pass (with the exception of the flaky `TestPgWireCredentialsReloadWithNewProp`, related to this...

> Whatever dynamic behaviour works in OSS also works with EE. I need to wire up EE to get this working... I'll give it a shot in a PR over...

Following up on this, the [UDP receiver has been deprecated](https://questdb.io/docs/reference/api/ilp/udp-receiver/) (since QuestDB version 6.5.2) so we recommend using the TCP receiver at this time. Which version of QuestDB are you...

Depends on https://github.com/questdb/questdb/issues/1925

I'm actually working on a similar package (https://github.com/sklarsa/django-sendgrid-v4) and am experiencing a `billiard`-related error in a celery task. I'm digging into it a little deeper now to see if I...

It actually looks like my error is matplotlib-related (different from yours)... Are all of your celery workers running the same version of `python_http_client`?

I'm actually getting the same error when passing in additional headers to the `EmailMultiAlternatives` constructor like so: `headers={"Reply-To": "[email protected]"}`. I wish I could get more debugging information from the exception...