totorofly

> Thanks! > > 1. Is 2k qps `json.set` is per single worker or overall? > 2. what's the average `ft.search` query load? > > Please note that Dragonfly does...

> one last question. Can you put here an example ft.search query that you run on your database? > > fyi, we currently do not support `ft.search` but we understand...

Same issue ``` "next": "^14.2.5", "react-toastify": "^10.0.5", ```

I conducted tests on version "@nytimes/react-prosemirror": "^0.3.0", and the issue still persists. > Ah, this is probably related to the IME composition issues that were brought up in #49? If...

> You'll have to specifically use `"@nytimes/react-prosemirror": "0.3.0-beta.0"` to get the new architecture! I tried switching to version 0.3.0-beta.0. The input indeed became possible, but when I used an IME...

I am very willing to cooperate with testing. However, when I used the address you provided and turned off the IME to use the system's default input, entering any letter...

> Ah! I was able to reproduce this on Chrome; it seems to be a difference in how Chrome and Firefox handle... something! Not sure yet, but this is very...

> Oh great, that's good to know! Starting a new line is definitely its own edge case in this situation Based on the current test results, 1) if a new...

Is there going to be a new release coming soon? I've been using Tiptap, but I've found that it supports Vue better than React, and I'm using Next.js based on...

> I am experiencing this same error in a Vite React app. It only appears when HMR refreshes (ie saving a file). This could be a duplicate issue though: #3580...