Skip to content

BACKPORT TO PATCH - fix(ivy): ngcc - handle missing entry-point dependencies better - #30323

Closed
petebacondarwin wants to merge 1 commit into
angular:8.0.xfrom
petebacondarwin:issue-29624-patch
Closed

petebacondarwin wants to merge 1 commit into
angular:8.0.xfrom
petebacondarwin:issue-29624-patch

Conversation

@petebacondarwin

Copy link
Copy Markdown
Contributor

Caretaker: This is a backport to patch of #30270 so it has been reviewed and presubmitted already.

If an entry-point has a missing dependency then all the entry-points
that would have pointed to that dependency are also removed from
the dependency graph.

Previously we were still processing the dependencies of an entry-point
even if it had already been removed from the graph because it depended
upon a missing dependency that had previously been removed due to another
entry-point depending upon it.

This caused the dependency processing to crash rather than gracefully
logging and handling the missing invalid entry-point.

Fixes angular#29624
@petebacondarwin petebacondarwin added type: bug/fix action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime PR target: patch-only merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels May 8, 2019
@petebacondarwin
petebacondarwin requested a review from a team May 8, 2019 07:26
@ngbot ngbot Bot modified the milestone: needsTriage May 8, 2019
@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 Sep 15, 2019
@petebacondarwin
petebacondarwin deleted the issue-29624-patch branch September 8, 2021 09:42
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 cla: yes merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note type: bug/fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants