Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFix nested modules while imported under more than 3 levels #27034
Conversation
highfive
commented
Jun 22, 2020
|
Heads up! This PR modifies the following files:
|
|
Opened new PR for upstreamable changes. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#24284. |
|
r? @jdm or @Manishearth |
|
Could you mention the commit range being reverted and PR in the first commit? |
Sorry, I don't actually revert a commit because it was squashed in the #26395; maybe it's good to just mention the PR? |
|
Hope the first new commit is clear enough |
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#24284. |
|
@CYBAI right, hence the mention of the commit range |
In https://github.com/servo/servo/pull/26395/files#diff-3fe97584f564214ec8e7ebbf91747e03L253-R318, we moved from `recursive checking` of dependency status to check only the _current module_'s dependency status and its descendant dependency status and also circular dependency status. However, it will cause an issue. For example, if the module dependency is like following ``` a -> b -> c -> d -> e f -> g -> h -> c -> d -> e ``` In this example, if the d module is still under fetching but g is trying to advance to finish. Then, it will cause a panic because module d is g's grand-grand-grand-descendant which means it's still under fetching and we can't instantiate module g. Ideally, we should get rid of the checking in #26903 so, before #26903 fixed, we can just move back to the recursive checking way which will ensure all descendants are not fetching.
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#24284. |
|
@Manishearth I'm still not so clear what you mean commit range here |
|
never mind, this is fine @bors-servo r+ |
|
|
Fix nested modules while imported under more than 3 levels This is kind of workaround to fix the issue but #26903 should provide much better solution to remove the checking. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27029 - [x] There are tests for these changes <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
|
|
@bors-servo retry |
Fix nested modules while imported under more than 3 levels This is kind of workaround to fix the issue but #26903 should provide much better solution to remove the checking. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #27029 - [x] There are tests for these changes <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
|
@bors-servo retry |
|
|
|
Error syncing changes upstream. Logs saved in error-snapshot-1592881946733. |
It might be caused by the CI failure? I saw this in
|
CYBAI commentedJun 22, 2020
This is kind of workaround to fix the issue but #26903 should provide much better solution to remove the checking.
./mach build -ddoes not report any errors./mach test-tidydoes not report any errors