Uh oh!
There was an error while loading. Please reload this page.
concurrent rendering name inconsistent #1202
Replies: 3 comments
That's a bug. Do you want to PR to change it to ASYNC? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm going to hold off on messing with concurrent rendering as it doesn't benefit me. I don't do any I/O calls in the render logic under normal circumstances and all hooks are already async. The cpu portion of the rendering isn't actually in parallel because of how asyncio works. |
I created a discussion around the concurrent rendering. Basically, I don't want to be the one to fix this because I feel like it's endorsing it when I'm not sure its providing value yet. If it does provide value, then I suggest just having one code route. My presumption is that this is a config option since it may have bugs? |
Uh oh!
There was an error while loading. Please reload this page.
All references to concurrent rendering use
ASYNCand even the instructions in the changelog say to use the environment variableREACTPY_ASYNC_RENDERING=truebut its actuallyREACTPY_CONCURRENT_RENDERING=trueAll reactions