|
1 | 1 | # Version (development version)
|
2 | 2 |
|
| 3 | +This is the fifth rollout out of several towards a near-future major |
| 4 | +release. This has been made possible due to a multi-year effort of |
| 5 | +internal re-designs, work with package maintainers, release, and |
| 6 | +repeat. This release fixes a few more regressions introduced in |
| 7 | +**future** 1.40.0 (2025-04-10) and 1.67.0 (2025-07-29). |
| 8 | + |
3 | 9 | ## Bug Fixes
|
4 | 10 |
|
5 | 11 | * The `cluster` backend failed when used with an `MPIcluster` as
|
6 | 12 | created by `parallel::makeCluster(..., type = "MPI")`. This bug was
|
7 | 13 | introduced in **future** (>= 1.40.0) [2025-04-10].
|
8 | 14 |
|
| 15 | + * Setting `R_FUTURE_PLAN=multisession` in an Renviron file, or a |
| 16 | + shell startup script, would result in a "fork bomb" when loading |
| 17 | + the **future** package. This happened because the setup of the |
| 18 | + future backend happened eagerly when the **future** package was |
| 19 | + loaded instead of being deferred to when the first future launched. |
| 20 | + This resulted in new, nested R workers being created recursively, |
| 21 | + until the machine ran out of resources. This bug was introduced in |
| 22 | + **future** (>= 1.67.0) [2025-07-29]. |
| 23 | + |
9 | 24 |
|
10 | 25 | # Version 1.67.0 [2025-07-29]
|
11 | 26 |
|
12 | 27 | This is the fourth rollout out of several towards a near-future major
|
13 | 28 | release. This has been made possible due to a multi-year effort of
|
14 | 29 | internal re-designs, work with package maintainers, release, and
|
15 |
| -repeat. This release fixes a few more regressions introduced in future |
16 |
| -1.40.0 (2025-04-10). |
| 30 | +repeat. This release fixes a few more regressions introduced in |
| 31 | +**future** 1.40.0 (2025-04-10). |
17 | 32 |
|
18 | 33 | ## Significant Changes
|
19 | 34 |
|
@@ -66,9 +81,9 @@ repeat. This release fixes a few more regressions introduced in future
|
66 | 81 | This is the third rollout out of several towards a near-future major
|
67 | 82 | release that I am really excited about. This has been made possible
|
68 | 83 | due to a multi-year effort of internal re-designs, work with package
|
69 |
| -maintainers, release, and repeat. This release fixes a few |
70 |
| -regressions introduced in future 1.40.0 (2025-04-10), despite passing |
71 |
| -[all unit, regression, and system |
| 84 | +maintainers, release, and repeat. This release fixes a few regressions |
| 85 | +introduced in **future** 1.40.0 (2025-04-10), despite passing [all |
| 86 | +unit, regression, and system |
72 | 87 | tests](https://www.futureverse.org/quality.html).
|
73 | 88 |
|
74 | 89 | ## New Features
|
@@ -142,8 +157,8 @@ tests](https://www.futureverse.org/quality.html).
|
142 | 157 | This is the second rollout out of three-four major updates, which is
|
143 | 158 | now possible due to a multi-year effort of internal re-designs, work
|
144 | 159 | with package maintainers, release, and repeat. This release fixes two
|
145 |
| -regressions introduced in future 1.40.0 (2025-04-10), despite passing |
146 |
| -[all unit, regression, and system |
| 160 | +regressions introduced in **future** 1.40.0 (2025-04-10), despite |
| 161 | +passing [all unit, regression, and system |
147 | 162 | tests](https://www.futureverse.org/quality.html) of the Future API
|
148 | 163 | that we have built up over the years. On the upside, fixing these
|
149 | 164 | issues led to a greatly improved static-code analyzer for
|
|
0 commit comments