-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
feat(vendor): support modifying remote files in vendor folder without checksum errors #23979
Conversation
// ideally the two error messages would be the same... this one comes from | ||
// deno_cache and the one above comes from deno_graph. The thing is, in deno_cache | ||
// (source of this error) it makes sense to include the url in the error message | ||
// because it's not always used in the context of deno_graph |
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.
Fixed!
if let Some(lockfile) = &self.lockfile { | ||
let mut lockfile = lockfile.lock(); | ||
// validate the integrity of all the modules | ||
graph_lock_or_exit(graph, &mut lockfile); |
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.
Handled in graph_roots_valid.
deno_graph = { version = "=0.75.2", features = ["tokio_executor"] } | ||
deno_doc = { version = "=0.137.0", features = ["html", "syntect"] } | ||
deno_emit = "=0.41.0" | ||
deno_graph = { version = "=0.77.0", features = ["tokio_executor"] } |
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.
It seems some wpt tests are failing due to denoland/deno_graph#483
See https://github.com/denoland/deno/actions/runs/9262872207
I'm unsure how to interpret the wpt test output. Are we incorrectly failing now?
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.
I have updated the expectations. We were previously failing these tests, now the tests pass. The expectations file was assuming the tests to fail though, so them passing caused the suite to fail.
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.
Thanks!
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.
LGTM, went through the PR 👍
Slight perf regression when updating deno_lockfile in #23979
Includes:
This is actually a lockfile perf investigation of moving the lockfile verification to be done in deno_graph's loader, but it has the side effect of enabling the ability to modify remote modules in the
vendor
folder without causing checksum errors.Benchmarks
With
"vendor": true
(note: this PR doesn't fix the underlying issue that makes this scenario slow... I will follow up with that later):With
"vendor": false
(slightly slower because it now has to verify checksums):