Skip to content

Show a proper error if a server function's bound args cannot be serialized #47488

Show a proper error if a server function's bound args cannot be serialized

Show a proper error if a server function's bound args cannot be serialized #47488

Re-run triggered December 3, 2024 16:20
Status Success
Total duration 13m 12s
Artifacts 179

build_and_test.yml

on: pull_request
Determine changes
10s
Determine changes
optimize-ci  /  Graphite CI Optimizer
29s
optimize-ci / Graphite CI Optimizer
build-native  /  build
31s
build-native / build
validate-docs-links
14s
validate-docs-links
Matrix: test unit
rustdoc check  /  build
3m 4s
rustdoc check / build
ast-grep lint
21s
ast-grep lint
test next-swc wasm  /  build
2m 18s
test next-swc wasm / build
test cargo benches  /  Test
5m 15s
test cargo benches / Test
test next-swc wasi  /  build
test next-swc wasi / build
test devlow package  /  build
test devlow package / build
Matrix: test prod
Matrix: test dev
Matrix: test integration
Matrix: Test new tests for flakes (dev)
Matrix: Test new tests for flakes (prod)
Matrix: test ppr dev
Matrix: test ppr prod
Matrix: test turbopack dev
Matrix: test turbopack development integration
Matrix: test turbopack production integration
Matrix: test turbopack production
test ppr integration  /  build
1m 49s
test ppr integration / build
test firefox and safari  /  build
4m 17s
test firefox and safari / build
types and precompiled  /  build
1m 38s
types and precompiled / build
Matrix: Run devlow benchmarks
Matrix: Test new tests when deployed
report test results to datadog
1m 4s
report test results to datadog
Fit to window
Zoom out
Zoom in

Annotations

20 warnings and 10 notices
Determine changes
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
validate-docs-links
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
optimize-ci / Graphite CI Optimizer
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ast-grep lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
no-vc-struct: turbopack/crates/turbopack-core/src/diagnostics/mod.rs#L114
Don't use a Vc directly in a struct
no-vc-struct: crates/next-api/src/route.rs#L33
Don't use a Vc directly in a struct
no-vc-struct: crates/next-api/src/route.rs#L34
Don't use a Vc directly in a struct
no-vc-struct: crates/next-api/src/route.rs#L37
Don't use a Vc directly in a struct
no-vc-struct: crates/next-api/src/route.rs#L42
Don't use a Vc directly in a struct
no-vc-struct: turbopack/crates/turbopack-core/src/source_map/mod.rs#L61
Don't use a Vc directly in a struct
no-vc-struct: turbopack/crates/turbopack-core/src/source_map/mod.rs#L95
Don't use a Vc directly in a struct
no-vc-struct: turbopack/crates/turbopack-core/src/source_map/mod.rs#L96
Don't use a Vc directly in a struct
no-vc-struct: turbopack/crates/turbopack-core/src/reference/mod.rs#L37
Don't use a Vc directly in a struct
no-vc-struct: turbopack/crates/turbopack-core/src/reference/mod.rs#L52
Don't use a Vc directly in a struct
rustdoc check / build: crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::Start`
rustdoc check / build: crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
rustdoc check / build: crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::End`
rustdoc check / build: crates/napi/src/next_api/project.rs#L950
public documentation for `project_update_info_subscribe` links to private item `UpdateMessage::Start`
thank you, next
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
report test results to datadog
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
to-resolved-in-loop: turbopack/crates/turbopack-core/src/reference/mod.rs#L180
Calling `RawModule::new(*source).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/reference/mod.rs#L195
Calling `module.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: crates/next-core/src/next_shared/transforms/swc_ecma_transform_plugins.rs#L54
Calling `project_path.root().to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/resolve/mod.rs#L1062
Calling `FileSource::new(**path).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/resolve/mod.rs#L1080
Calling `FileSource::new(**path).to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/resolve/mod.rs#L2262
Calling `Request::parse(Value::new(Pattern::Constant(request)))
to-resolved-in-loop: turbopack/crates/turbopack-dev-server/src/source/asset_graph.rs#L180
Calling `asset.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-core/src/rebase.rs#L55
Calling `RebasedAsset::new(*module, *self.input_dir, *self.output_dir)
to-resolved-in-loop: turbopack/crates/turbopack-css/src/chunk/mod.rs#L272
Calling `chunk_item_key.to_resolved().await?` in a loop could be a doing a lot of work sequentially. Consider producing an iterator of futures and using `try_join`.
to-resolved-in-loop: turbopack/crates/turbopack-css/src/chunk/mod.rs#L316
Calling `SingleItemCssChunk::new(*this.chunking_context, **item)

Artifacts

Produced during runtime
Name Size
test-playwright-snapshots-test-dev-react--3-4 Expired
1.3 MB
test-playwright-snapshots-test-turbopack-production-integration-2-5 Expired
1.84 MB
test-reports-test-dev-react--3-4 Expired
131 KB
test-reports-test-turbopack-production-integration-2-5 Expired
54.6 KB
turbo-run-summary-test-dev-react--3-4 Expired
238 KB
turbo-run-summary-test-turbopack-production-integration-2-5 Expired
238 KB