Ahmet Enes Bayraktar

@krynble AWS Serverless Redis uses cluster mode you can try to connect with `redis-cli -c`. I am also having this issue and I tried using `QUEUE_BULL_REDIS_HOST` but n8n fails

Sorry for late reply, > Is it possible for you to try the regular redis deployment instead of the serverless option? I think this is a simpler deployment that would...

We also would appreciate such feature

It would be nice if we can use `home:uri` variable as well

This is not working, am I doing something wrong? ```toml [tool.hatch.envs.default] path = "{home:uri}/.virtualenvs" ```

Having the same issue. I am trying the following docs: https://learn.microsoft.com/en-us/azure/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller?tabs=install-helm-windows https://learn.microsoft.com/en-us/azure/application-gateway/for-containers/quickstart-create-application-gateway-for-containers-managed-by-alb-controller?tabs=new-subnet-aks-vnet The result is the same error. I can see the resources on azure-portal but I am not sure...

I do not know how the internals work but since it can already detected can't it be ordered easily?   

It is from `dart analyzer`. `dart fix --apply` fixes the warning

You can use this: https://github.com/aeb-dev/flame_steamworks/tree/main/example

Step 1: Clone this repo: https://github.com/aeb-dev/dart_pub_gitignore_nested Step 2: Run example once Step 3: `flutter pub publish --dry-run`