Skip to content

refactor(core): Do not duplicate change detection with run coalescing (part 2) - #55403

Closed
atscott wants to merge 1 commit into
angular:mainfrom
atscott:runcoalescing2
Closed

atscott wants to merge 1 commit into
angular:mainfrom
atscott:runcoalescing2

Conversation

@atscott

@atscott atscott commented Apr 18, 2024

Copy link
Copy Markdown
Contributor

This commit prevents doubling change detections when the zoneless scheduler is notified first, followed by the zone becoming unstable (effectively "scheduling" zone-based change detection). When run coalescing is enabled, this would otherwise result in the zoneless scheduler running change detection first and then change detection running again because of the run coalescing since both scheduler use the same timing function (and then it would be FIFO).

@atscott atscott added the target: minor This PR is targeted for the next minor release label Apr 18, 2024
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Apr 23, 2024
@atscott

atscott commented Apr 24, 2024

Copy link
Copy Markdown
Contributor Author

presubmit

@atscott atscott added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Apr 24, 2024
@atscott

atscott commented Apr 24, 2024

Copy link
Copy Markdown
Contributor Author

caretaker note: CI failure is failing at HEAD, not from this PR

@thePunderWoman thePunderWoman added the area: core Issues related to the framework runtime label Apr 24, 2024
@ngbot ngbot Bot added this to the Backlog milestone Apr 24, 2024
… (part 2)

This commit prevents doubling change detections when the zoneless
scheduler is notified first, followed by the zone becomeing unstable
(effectively "scheduling" zone-based change detection). When run
coalescing is enabled, this would otherwise result in the zoneless
scheduler running change detection first and then change detection
running again because of the run coalescing since both scheduler use the
same timing function (and then it would be FIFO).
@atscott atscott removed the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Apr 24, 2024
@AndrewKushnir AndrewKushnir added target: rc This PR is targeted for the next release-candidate and removed target: minor This PR is targeted for the next minor release labels Apr 25, 2024
@AndrewKushnir

Copy link
Copy Markdown
Contributor

This PR was merged into the repository by commit 356ec65.

AndrewKushnir pushed a commit that referenced this pull request Apr 25, 2024
… (part 2) (#55403)

This commit prevents doubling change detections when the zoneless
scheduler is notified first, followed by the zone becomeing unstable
(effectively "scheduling" zone-based change detection). When run
coalescing is enabled, this would otherwise result in the zoneless
scheduler running change detection first and then change detection
running again because of the run coalescing since both scheduler use the
same timing function (and then it would be FIFO).

PR Close #55403
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants