Jesse

We're not going to work on this until at least after the V10 release later this summer. Later this year we'll introduce some processes for improving work planning with the...

No update to share at this time. But we have not forgotten about this use case. > and no need to catch it into postgresql. The results are always cached....

I'm not clear what is your request: to add a new visualisation type or a new query runner for kepler?

Sorry to only now respond. The problem is you have many jobs running and not enough workers to handle them. Your `docker-compose.yml` shows no workers are dedicated to running _only_...

Sorry to only just get to this. Yep this is a real bug and your reproduction steps are correct. I've self-assigned [edit] What is the desired behaviour in this case?

Sorry to only now see this. When you say the queries "fail", do you receive a specific error from Redash? Or do they just take a long time before eventually...

Thanks for the ping. I've been out after surgery. Will put eyes on this ASAP.

Have you confirmed that the front-end tests pass with these changes? I'm seeing lots of red under the build checks and want to make sure this works on your machine...

What platform are you running? If you're running MacOS Monterey you will need to change the default ports from `5000` because the OS now uses this port.

Did you recently change the names of the groups in your organization? The error seems like you may have renamed the `default` group to something else.