Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix missing content key in symbol prop when asset is removed #9627

Merged
merged 3 commits into from
Apr 8, 2024

Conversation

mattcompiles
Copy link
Contributor

↪️ Pull Request

This PR addresses a bug in incremental symbol propagation where assets are requested for propagation even if they are no longer contained within the AssetGraph. This can happen in the following circumstance:

  • Build fails during the AssetGraphRequest but finds some new Assets for propagation
  • Next build runs but the previously discovered Assets are no longer in the AssetGraph (e.g. removed import)

🚨 Test instructions

Integration test added

✔️ PR Todo

  • Added/updated unit tests for this change
  • Filled out test instructions (In case there aren't any unit tests)
  • Included links to related issues/PRs


let {bundleGraph} = await b.run();

assert(await run(bundleGraph), 'ITS WORKING');
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm assuming without your change this test fails with the "missing key in symbol propagation" error we've been seeing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's right 😄

Copy link
Contributor

@marcins marcins left a comment

Choose a reason for hiding this comment

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

Nice find and fix!

@mattcompiles mattcompiles merged commit 2aa753c into v2 Apr 8, 2024
15 of 17 checks passed
@mattcompiles mattcompiles deleted the fix-missing-content-key-symbol-prop branch April 8, 2024 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants