- Issue created by @kingdutch
- Merge request !6865Issue #3425114: Add revolt/event-loop dependency to core β (Open) created by kingdutch
- Status changed to Needs review
7 months ago 12:27pm 2 March 2024 - π¬π§United Kingdom catch
+1 to this. Having looked at (but not actually tried to use) the react/amp projects I'm not sure how useful those will be for us, but revolt is a layer below both of those, and would save us copying the fiber foreach loops around as we slowly introduce async support into more places.
Taking the RM review tag off, but leaving the FM review tag on so this gets a +1 from another core committer who's not me.
- Status changed to Needs work
6 months ago 4:12am 3 April 2024 The Needs Review Queue Bot β tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide β to find step-by-step guides for working with issues.
- First commit to issue fork.
- Status changed to Needs review
about 2 months ago 1:55pm 9 August 2024 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Do we have a list or meta somewhere of places we want to use async for?
- π«π·France andypost
Yes, there's 2 issues blocked on it, listed in "Referenced by"
π [PP-1] Ensure asynchronous tasks that run beyond the length of a request have the chance to complete before process exit Active
π [PP-2] Migrate BigPipe and Renderer fiber implementation to use Revolt Event Loop Postponed - π¬π§United Kingdom catch
π± [meta] Use Fibers for concurrency in core Active is the meta.
- Status changed to RTBC
11 days ago 2:34pm 17 September 2024 - πΊπΈUnited States smustgrave
Last 2 remaining tasks have been resolved (updated IS with comments they were)
Dependency evaluation appears complete and has gotten multiple +1s.
Going out on a limb and marking.