test: fix type error in segment-cache-basic test #48425
Annotations
5 warnings and 10 notices
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
ast-grep lint step:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_static.rs#L8
Don't use a Vc directly in a struct
|
|
ast-grep lint step:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_inherent_impl.rs#L11
Don't use a Vc directly in a struct
|
|
ast-grep lint step:
turbopack/crates/turbo-tasks-macros-tests/tests/function/fail_non_local_trait_impl.rs#L11
Don't use a Vc directly in a struct
|
|
ast-grep lint step:
turbopack/crates/turbo-tasks-macros-tests/tests/value/fail_non_local.rs#L8
Don't use a Vc directly in a struct
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/reference/mod.rs#L184
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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/rebase.rs#L55
Calling `RebasedAsset::new(*module, *self.input_dir, *self.output_dir)
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L77
Calling `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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L95
Calling `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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L105
Calling `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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/introspect/utils.rs#L127
Calling `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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-core/src/code_builder.rs#L167
Calling `encoded.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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-css/src/chunk/mod.rs#L271
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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-css/src/chunk/mod.rs#L453
Calling `entry_module_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`.
|
|
ast-grep lint step:
turbopack/crates/turbopack-swc-utils/src/emitter.rs#L32
Calling `issue.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`.
|
Loading