Add Support for Caching Stylus Programs in Cargo Stylus #170
rauljordanAnnotations
3 errors and 6 warnings
|
(x86_64-unknown-linux-gnu, nightly)
Process completed with exit code 101.
|
|
(x86_64-unknown-linux-gnu, stable)
The job was canceled because "x86_64-unknown-linux-gnu_" failed.
|
|
(x86_64-unknown-linux-gnu, stable)
The operation was canceled.
|
|
field `rebuild` is never read:
check/src/project.rs#L33
warning: field `rebuild` is never read
--> check/src/project.rs:33:9
|
30 | pub struct BuildConfig {
| ----------- field in this struct
...
33 | pub rebuild: bool,
| ^^^^^^^
|
= note: `BuildConfig` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis
= note: `#[warn(dead_code)]` on by default
|
|
unused import: `ARB_WASM_ADDRESS`:
check/src/check.rs#L6
warning: unused import: `ARB_WASM_ADDRESS`
--> check/src/check.rs:6:17
|
6 | constants::{ARB_WASM_ADDRESS, ARB_WASM_H160, ONE_ETH},
| ^^^^^^^^^^^^^^^^
|
= note: `#[warn(unused_imports)]` on by default
|
|
field `status` is never read:
replay/src/trace.rs#L408
warning: field `status` is never read
--> replay/src/trace.rs:408:9
|
407 | UserReturned {
| ------------ field in this variant
408 | status: u32,
| ^^^^^^
|
|
field `args_len` is never read:
replay/src/trace.rs#L405
warning: field `args_len` is never read
--> replay/src/trace.rs:405:9
|
404 | UserEntrypoint {
| -------------- field in this variant
405 | args_len: u32,
| ^^^^^^^^
|
|
field `receipt` is never read:
replay/src/trace.rs#L23
warning: field `receipt` is never read
--> replay/src/trace.rs:23:9
|
21 | pub struct Trace {
| ----- field in this struct
22 | pub top_frame: TraceFrame,
23 | pub receipt: TransactionReceipt,
| ^^^^^^^
|
= note: `Trace` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
= note: `#[warn(dead_code)]` on by default
|
|
(x86_64-unknown-linux-gnu, nightly)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|