-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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: add support for --parallel #6339
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
10 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
🟢 CI successful 🟢Thanks |
@@ -120,6 +120,32 @@ impl PackageGraph { | |||
Ok(graph::validate_graph(&self.workspace_graph)?) | |||
} | |||
|
|||
pub fn no_workspace_dependencies(self) -> Self { |
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.
Is remove_workspace_dependencies
a better name?
|
||
if let Some(graph_opts) = opts.run_opts.graph { | ||
match graph_opts { | ||
GraphOpts::File(graph_file) => { |
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.
just making sure i understand this arm... it's not actually writing the graph to a file yet right? I don't see the engine
or pkg_dep_graph
used in here
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.
Correct, one of the features left is support for non-DOT
--graph
support. The todo
macro call in this branch will panic when hit.
|
||
if !opts.run_opts.parallel { | ||
engine | ||
.validate(pkg_dep_graph, opts.run_opts.concurrency) |
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.
Just a note that we should fix #4291 with this in the future. I think it's fine to only fix in Rust if we're close
Description
This PR hooks up the correct behavior of
--parallel
Some code shuffling happens in the first few commits to get the Rust
run
function in a closer shape the Go code.Testing Instructions
npx create-turbo
npm rm turbo
build
script topackages/ui/package.json
:"build": "echo 'building'; sleep 5; echo 'done'",
turbo_dev build --parallel --experimental-rust-codepath
should show thatdocs#build
andweb#build
start beforeui#build
is finished even though they depend on theui
workspaceCloses TURBO-1566