Skip to content

Add Dagger.spawn, allow on any node #217

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

Merged
merged 7 commits into from
May 20, 2021
Merged

Add Dagger.spawn, allow on any node #217

merged 7 commits into from
May 20, 2021

Conversation

jpsamaroo
Copy link
Member

@jpsamaroo
Copy link
Member Author

Slight complication: if we want to do nested @spawn, we need some way to ensure that the thunk we're trying to wait/fetch gets scheduled before our thunk completes. Logically, the right thing to do is to teach the scheduler to temporarily reduce the spawning thunk's pressure to 0 so that the new thunk has capacity to execute (and once we finish waiting, we set it back to its original value).

@jpsamaroo jpsamaroo merged commit 9c01b65 into master May 20, 2021
@jpsamaroo jpsamaroo deleted the jps/better-spawn branch May 20, 2021 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow Dagger.@spawn on non-head node
1 participant