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: avoid caching transform result of invalidated module #7254

Merged
merged 1 commit into from Mar 10, 2022

Conversation

patak-dev
Copy link
Member

Description

See #7243 for more context and a bug reproduction. Splitting this from there as they aren't related. And we can keep discussing here about this issue.

When we call moduleGraph.invalidateAll() before doing the full-reload after re-processing, there are requests that are on the fly and end up updating their module info... so when the browser requests them after the full reload... these modules are stale. @vursen this is what we were seeing in Vaadin with the 504 errors in the browser that didn't disappear even when reloading the page manually.

We need that a full-reload call will also stop every currently processing request to avoid modifying the module graph.

I think this could have been also present before, but now it is more visible because we aren't blocking the requests as before while processing. So a solution here may fix hard-to-replicate issues that we got in the past.


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

@patak-dev patak-dev requested a review from bluwy March 10, 2022 14:22
@patak-dev patak-dev added the p4-important Violate documented behavior or significantly improves performance (priority) label Mar 10, 2022
@patak-dev patak-dev added this to the 2.9 milestone Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p4-important Violate documented behavior or significantly improves performance (priority)
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

2 participants