Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add lock for render pass if we want to use a non-single threaded CoroutineDispatcher in the context for the runtime. #1259

Open
steve-the-edwards opened this issue Jan 30, 2025 · 0 comments

Comments

@steve-the-edwards
Copy link
Contributor

Otherwise, worker output (or anything sending to the sink like actions too) could happen during a render pass and we would get a lot of:

java.lang.UnsupportedOperationException: Expected sink to not be sent to until after the render pass. Received action: EmitWorkerOutputAction(worker=TypedWorker(), key=my_worker)

If we lock handling actions in the sink during the render pass then we could allow this parallelism.

For now we can only handle single-threaded dispatchers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant