[Rust] fix segfault caused by null pointer in hdfs #1418
Annotations
14 warnings and 1 notice
Post Set up JDK 11
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
|
Run actions-rs/cargo@v1
`lakesoul-io` (lib) generated 4 warnings
|
Run actions-rs/cargo@v1
struct `ProjectionStream` is never constructed
|
Run actions-rs/cargo@v1
method `batch_project` is never used
|
Run actions-rs/cargo@v1
unused variable: `e`
|
Run actions-rs/cargo@v1
unused variable: `v`
|
Run actions-rs/cargo@v1
`lakesoul-metadata` (lib) generated 2 warnings
|
Run actions-rs/cargo@v1
hiding a lifetime that's elided elsewhere is confusing
|
Run actions-rs/cargo@v1
hiding a lifetime that's elided elsewhere is confusing
|
Run Swatinem/rust-cache@v2
Cache not found for keys: v0-rust-build-windows-x86_64-Windows_NT-x64-5580836b-299171fc, v0-rust-build-windows-x86_64-Windows_NT-x64-5580836b
|
Run actions-rs/toolchain@v1
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run actions-rs/toolchain@v1
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run actions-rs/toolchain@v1
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Run actions-rs/toolchain@v1
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Loading