fix(#411): optimize contract gas costs with storage packing and bit f… #92
Annotations
20 errors and 8 warnings
|
fuzz / subscription
Process completed with exit code 101.
|
|
fuzz / subscription
cannot find attribute `rustc_layout_scalar_valid_range_end` in this scope
|
|
fuzz / subscription
cannot find attribute `rustc_layout_scalar_valid_range_start` in this scope
|
|
fuzz / subscription
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / subscription
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / pricing
Process completed with exit code 101.
|
|
fuzz / pricing
cannot find attribute `rustc_layout_scalar_valid_range_end` in this scope
|
|
fuzz / pricing
cannot find attribute `rustc_layout_scalar_valid_range_start` in this scope
|
|
fuzz / pricing
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / pricing
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / rate_limit
Process completed with exit code 101.
|
|
fuzz / rate_limit
cannot find attribute `rustc_layout_scalar_valid_range_end` in this scope
|
|
fuzz / rate_limit
cannot find attribute `rustc_layout_scalar_valid_range_start` in this scope
|
|
fuzz / rate_limit
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / rate_limit
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / state_machine
Process completed with exit code 101.
|
|
fuzz / state_machine
cannot find attribute `rustc_layout_scalar_valid_range_end` in this scope
|
|
fuzz / state_machine
cannot find attribute `rustc_layout_scalar_valid_range_start` in this scope
|
|
fuzz / state_machine
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / state_machine
attributes starting with `rustc` are reserved for use by the `rustc` compiler
|
|
fuzz / subscription
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzz / subscription
The process '/usr/bin/git' failed with exit code 128
|
|
fuzz / pricing
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzz / pricing
The process '/usr/bin/git' failed with exit code 128
|
|
fuzz / rate_limit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzz / rate_limit
The process '/usr/bin/git' failed with exit code 128
|
|
fuzz / state_machine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzz / state_machine
The process '/usr/bin/git' failed with exit code 128
|