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
{{ message }}
Repository navigation
Backport ALS to use AsyncContextFrame as default for v22 #60102
The change did break existing code (#58204). While it would likely be an improvement in most cases, I am hesitant to suggest to go for that due to that.
Reacted by Tim Fish, Matteo Collina and surajtaghash
Well, enterWith(...) is experimental and from day one had a big doc warning to never use it. It also arguably fixed a bug in the prior behaviour. 🤷🏻
But if others feel the change should be held back from backporting anyway I would not push for it. I think it's fine personally, though I don't feel strongly that it needs backporting necessarily. I'm all for more excuses to tell people they should upgrade. 🙈
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
[-]Backport `AsyncContextFrame` as default to v22[/-][+]Backport ALS to use `AsyncContextFrame` as default for v22[/+]Qard commentedon Oct 2, 2025
Sounds good to me. Haven't seen any issues arise since the change. 🙂
BridgeAR commentedon Oct 5, 2025
The change did break existing code (#58204). While it would likely be an improvement in most cases, I am hesitant to suggest to go for that due to that.
Qard commentedon Oct 7, 2025
Well,
enterWith(...)is experimental and from day one had a big doc warning to never use it. It also arguably fixed a bug in the prior behaviour. 🤷🏻But if others feel the change should be held back from backporting anyway I would not push for it. I think it's fine personally, though I don't feel strongly that it needs backporting necessarily. I'm all for more excuses to tell people they should upgrade. 🙈
github-actions commentedon May 6, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jun 5, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.