clippy stuff #167
Annotations
38 warnings
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build (ubuntu-latest)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
build (ubuntu-latest)
/home/runner/work/d4-format/d4-format/d4tools/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition
|
build (ubuntu-latest):
d4-hts/src/alignment/htslib.rs#L10
unexpected `cfg` condition name: `no_bam_hdr_destroy`
|
build (ubuntu-latest)
`d4-hts` (lib) generated 1 warning
|
build (ubuntu-latest)
`d4` (lib) generated 1 warning
|
build (ubuntu-latest):
d4tools/src/stat/main.rs#L264
value assigned to `print_header` is never read
|
build (ubuntu-latest)
`d4tools` (bin "d4tools") generated 1 warning
|
build (ubuntu-latest)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
build (ubuntu-latest)
/home/runner/work/d4-format/d4-format/d4tools/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition
|
build (ubuntu-latest):
d4-hts/src/alignment/htslib.rs#L10
unexpected `cfg` condition name: `no_bam_hdr_destroy`
|
build (ubuntu-latest)
`d4-hts` (lib) generated 1 warning
|
build (ubuntu-latest)
`d4` (lib) generated 1 warning
|
build (ubuntu-latest)
`d4tools` (bin "d4tools") generated 1 warning
|
build (ubuntu-latest)
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/
|
build (ubuntu-latest)
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/
|
build (ubuntu-latest)
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/
|
build (ubuntu-latest)
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/
|
build (macos-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build (macos-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build (macos-latest)
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/
|
build (macos-latest)
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/
|
build (macos-latest)
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/
|
build (macos-latest)
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/
|
build (macos-latest)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
build (macos-latest)
/Users/runner/work/d4-format/d4-format/d4tools/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition
|
build (macos-latest):
d4-hts/src/alignment/htslib.rs#L10
unexpected `cfg` condition name: `no_bam_hdr_destroy`
|
build (macos-latest)
`d4-hts` (lib) generated 1 warning
|
build (macos-latest)
`d4` (lib) generated 1 warning
|
build (macos-latest):
d4tools/src/stat/main.rs#L264
value assigned to `print_header` is never read
|
build (macos-latest)
`d4tools` (bin "d4tools") generated 1 warning
|
build (macos-latest)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
build (macos-latest)
/Users/runner/work/d4-format/d4-format/d4tools/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition
|
build (macos-latest):
d4-hts/src/alignment/htslib.rs#L10
unexpected `cfg` condition name: `no_bam_hdr_destroy`
|
build (macos-latest)
`d4-hts` (lib) generated 1 warning
|
build (macos-latest)
`d4` (lib) generated 1 warning
|
build (macos-latest)
`d4tools` (bin "d4tools") generated 1 warning
|