Skip to content

Aderyn fails to run in Osaka-compatible project despite correct configuration #1082

@izcoser

Description

@izcoser

Describe the bug
I am trying to run Aderyn in an Osaka-vm project, Aderyn fails saying the instruction is only available for Osaka compatible VMs, but it is configured to use osaka.

To Reproduce
Steps to reproduce the behavior:

  1. Clone repo: https://github.com/morpho-org/midnight
  2. Run aderyn
  3. See error:
------------------------------------------------------------------------------------
# Configuration
------------------------------------------------------------------------------------
Root - /home/user/venturus/eagle_workspaces/coser@gmail.com/midnight
Source - /home/user/venturus/eagle_workspaces/coser@gmail.com/midnight/src
Remappings - [
    "forge-std/=lib/forge-std/src/",
]
EVM version - osaka
------------------------------------------------------------------------------------
# Source Scope
------------------------------------------------------------------------------------
Include Filepaths Containing - No specific criteria.
Exclude Filepaths Containing - No specific criteria.
Auto Excluding - No Files.
------------------------------------------------------------------------------------
# Compiling Abstract Syntax Trees
------------------------------------------------------------------------------------
Compilation Error: Error (4948): The "clz" instruction is only available for Osaka-compatible VMs (you are currently compiling for "prague").
  --> src/libraries/UtilsLib.sol:56:29:
   |
56 |             res := sub(255, clz(bitmap))
   |                             ^^^

As you see, it detects EVM version as osaka but fails to compile saying it has to be osaka compatible and compiles for prague.

Expected behavior
Report comes out.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • arch linux
  • amd
  • aderyn 0.6.8

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions