Error on use of self intead of Self in return type (#6763) #3312
Annotations
4 errors and 20 warnings
deploy
RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
|
deploy
No such remote: 'origin'
|
deploy
failed to push some refs to 'https://github.com/FuelLabs/sway.git'
|
deploy
Action failed with "The process '/usr/bin/git' failed with exit code 1"
|
deploy
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0
|
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: Swatinem/rust-cache@v1, 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/
|
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, Swatinem/rust-cache@v1, actions-rs/toolchain@v1, actions-rs/cargo@v1, peaceiris/actions-mdbook@v1, peaceiris/actions-gh-pages@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
deploy
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/
|
deploy
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/
|
deploy
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/
|
deploy
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/
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
package `futures-util v0.3.25` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|
deploy
The `save-state` 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/
|
deploy
The `save-state` 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/
|
deploy
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/
|
deploy
package `url v2.5.3` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
|