Jascha Brinkmann

This issue still exists and as far as I can see nobody has actually tried to confirm it but several people have run into this

Pretty sad about this as it basically means remix won't support `useBlocker` and `usePrompt` any longer. This is a very controversial discussion over here: https://github.com/remix-run/react-router/issues/8139#issuecomment-1262630360

I was actually wondering about this. It seems that `docker-flow-proxy-letsencrypt` always reissues and creates new secrets with the certificates when restarted, even so there are still valid certificates available. Is...

I am using secrets and a persistent volume as explained in http://proxy-letsencrypt.dockerflow.com/example-secrets/. But still my certificates are regenerated each time `dfple` is restarted. Seems like a bug to me.

@Vad1mo Yes it's correctly mounted to `/etc/letsencrypt`. And if I check the contents of the volume I can see that the certificates are correctly added to the volume. This only...

This was fixed for me in `[email protected]` https://github.com/remix-run/remix/issues/2987

Trying to use @prithvin suggested solition using `ioredis-mock` but with `bull:v3`. If I add a job with options like `queue.add( 'name', {}, { delay: 900000 } )` I get a...

@stigvanbrabant I didn’t and ended up switching to bullmq and just starting a Docker container with redis before running the test suite.

Any alternatives beside using the fork?

@ittechsathish Make sure to follow the [steps here](https://firebase.google.com/docs/functions/local-emulator#serve_http_functions_from_the_command_line), especially running this within your functions directory: ``` firebase functions:config:get > .runtimeconfig.json ``` Of course you have to make sure before that...