Samy Pessé
Samy Pessé
@JPeColCom Sorry for being late. This PR seems to be doing much more than just adding MSI support. Can you explain why all of these changes are required?
Or a way to pass a custom fetch (https://github.com/upstash/upstash-redis/blob/main/pkg/http.ts#L187) function in the constructor will be a good workaround
I took a look at https://github.com/upstash/upstash-redis/pull/783 and this is exactly what we are looking for 👍
Having a signal at the client level will not be great for us (client is defined as a global variable), but we'll make it work, it's better than not having...
Sorry, It's been some crazy time since I was working both on [Codebox](https://www.codebox.io) and [GitBook](https://www.gitbook.com), but I'll now be more focus on GitBook and I'll do my best to continue...
@ekatzenstein I'm not sure this module can work on client side, since it depends on `request`. But i'll be happy to merge a fix.
> Do we want to have all the message in one websocket connection in the same trace? Or have different traces? One that could work well for us is one...
@evanderkoogh, anything we can help with on this issue? If you have hints on the direction you'd like to take with the implementations, I can look at opening a PR
@AaronO Can you setup a webhook on Bob for this?
In the mid time, I manually pushed `gitbook/nuts:3.1.1` (https://hub.docker.com/r/gitbook/nuts/)