Shripad Krishna
Shripad Krishna
Just wanted to bump this issue as It is still not fixed in 0.26.2. My builds started failing post dependency upgrade from 0.25.1. Have reverted the version back to 0.25.1...
Has this issue actually been fixed? I tried it on my mobile now (Android) and it isn't working.
The right way of ensuring double WebSocket connections are not created is to track it as a global variable attached to the `window` object. Since you must have only 1...
I am currently doing it this way though I prefer using `Chroma.fromDocuments` instead: ```tsx const client = new ChromaClient(); const chroma = new Chroma( { collectionName, numDimensions, }, embeddings, client...
@nfcampos Thank you!
@alexsherstinsky thanks for the heads up. I'll definitely take a look at it and get back to you on this. Will surely keep an eye on the release. Thanks again...
+1. Would be great if the mode is configureable.
Broken for me as well!
I am able to use Cloudflare Tunnels for this and it works great for the most part. However, there is still an issue of live-reload websocket server pointing to the...
@oliviertassinari I stumbled upon this issue as well. Could something like this be possible? Assuming I want to add a new prop to say the Avatar component: prop is "size"...