You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was so far blocked, because we need all code, and especially side effects and outbound calls to live happily concurrently on one instance, sharing the same IP address, disc and everything else.
This has bitten us a couple of times, probably including:
I say "probably" because on live shiny apps it's very hard to test this, because two requests would have to come at the exact same time if run async, and that can make the bug appear intermittently
There's also the issue of whether this works with cr tracked separately in #135.
Before getting the async shiny in #42 to work (which isn't hard), we should test whether we have to expect/fix any concurrency issues, so that doesn't bite us again.
The text was updated successfully, but these errors were encountered:
we really need async renders asap #42 now.
This was so far blocked, because we need all code, and especially side effects and outbound calls to live happily concurrently on one instance, sharing the same IP address, disc and everything else.
This has bitten us a couple of times, probably including:
I say "probably" because on live shiny apps it's very hard to test this, because two requests would have to come at the exact same time if run async, and that can make the bug appear intermittently
There's also the issue of whether this works with cr tracked separately in #135.
Before getting the async shiny in #42 to work (which isn't hard), we should test whether we have to expect/fix any concurrency issues, so that doesn't bite us again.
The text was updated successfully, but these errors were encountered: