fix: tests in CI - #1034
Merged
Merged
Conversation
added 15 commits
February 23, 2022 17:55
alanshaw
marked this pull request as ready for review
February 24, 2022 12:57
vasco-santos
approved these changes
Feb 24, 2022
vasco-santos
left a comment
Member
There was a problem hiding this comment.
LGTM
Thanks for jumping into this Alan
This was referenced Feb 24, 2022
This file contains hidden or 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.
Node.js v16.14.0 included a fix that meant that
@web-std/blobstarted using the Node.js native version.Bad news, Node.js currently copies the buffer on every iteration when obtaining a stream from
File.stream(). It also has a fixed and small chunk size of65536bytes. This makes reading the stream VERY slow and this test fails because it times out.I opened an issue about this here: nodejs/node#42108
Once the test was fixed, the cloudflare build for the website started failing so I had to update next.js to v12. WTF!?!
After that, the client build started failing with:
So I had to roll the update to
parse-link-headerfrom #1032 into here as well.