Fix vulnerable packages + Transient errors in tests #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think I finally found a problem that has been killing me for the past months, since tests we failing randomly, which seems to have to do with Promises not being flushed when using mock timers (which was the case in the ApplicationReviewWidget tests)
Some relevant info may be found here:
The solution involved migrating to the new implementation of fake timers from Jest 26 https://jestjs.io/blog/2020/05/05/jest-26#new-fake-timers
Regarding the audit issue, it was a problem with the react-dev-utils package (facebook/create-react-app#10411). Fixed by upgrading its version as well to 11.0.3