-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix TLA: module should wait for its async dependencies #2488
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
base: main
Are you sure you want to change the base?
Conversation
File size impactMerging kz/top-level-await-fix into main will impact 3 files in 2 groups. browser (2/2)
node (1/1)
extras (0/8)No impact on files in extras group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for looking into this. Because this is a very complex algorithm, I think just having one test case is not enough to prove we aren't introducing other regressions.
For better testing I would advise looking at cases from the TLA fuzzer at https://github.com/evanw/tla-fuzzer, and trying to incorporate some more and show that this overall improves conformance over degraging it.
if (!process.env.SYSTEM_PRODUCTION) triggerOnload(loader, load, load.er, true); | ||
triggerOnload(loader, load, load.er, true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The onload event is only for the non-production build.
|
||
return doExec(); | ||
if (depLoadPromises) { | ||
return load.E = Promise.all(depLoadPromises).then(doExec).finally(function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is quite a big algorithmic change, that will likely have repercussions. I think to be comfortable making these kinds of algorithmic changes it would help to see much more test cases being checked.
I've also pushed a change to main to fix the broken CI. |
Reopening #2402 since the case is still valid.
Addresses: #2473
Here's the test results without the changes applied:
