Skip to content

fix(ngcc): do not crash if missing entry-point dependencies - #30270

Closed
petebacondarwin wants to merge 3 commits into
angular:masterfrom
petebacondarwin:issue-29624
Closed

petebacondarwin wants to merge 3 commits into
angular:masterfrom
petebacondarwin:issue-29624

Conversation

@petebacondarwin

@petebacondarwin petebacondarwin commented May 5, 2019 •

Copy link
Copy Markdown
Contributor

Fixes #29624

@petebacondarwin
petebacondarwin requested a review from a team May 5, 2019 14:58
@petebacondarwin
petebacondarwin force-pushed the issue-29624 branch 2 times, most recently from 330bf8f to bf202d4 Compare May 5, 2019 15:03
@kara kara added the comp: ivy label May 6, 2019
@ngbot ngbot Bot added this to the needsTriage milestone May 6, 2019
@petebacondarwin
petebacondarwin force-pushed the issue-29624 branch 2 times, most recently from f3c8653 to a6cd03b Compare May 6, 2019 21:15
@petebacondarwin petebacondarwin changed the title fix(ngcc): do not crash if missing entry-point depedencies fix(ngcc): do not crash if missing entry-point dependencies May 7, 2019

@gkalpak gkalpak left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message typo: "Previously we still processing"

Comment thread packages/compiler-cli/ngcc/src/main.ts Resolved
@gkalpak gkalpak added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label May 7, 2019
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 action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels May 7, 2019
@kara kara added target: major This PR is targeted for the next major release and removed target: patch This PR is targeted for the next patch release labels May 7, 2019
@kara

kara commented May 7, 2019

Copy link
Copy Markdown
Contributor

@petebacondarwin Can you make a patch-only version of this PR? It doesn't apply cleanly.

@kara kara closed this in f5b2ae6 May 7, 2019
kara pushed a commit that referenced this pull request May 7, 2019
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 #29624

PR Close #30270
@petebacondarwin

Copy link
Copy Markdown
Contributor Author

Done here #30323

@petebacondarwin
petebacondarwin deleted the issue-29624 branch May 8, 2019 07:27
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…lar#30270)

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

PR Close angular#30270
@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
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 cla: yes target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NGCC Error: Node does not exist

4 participants