Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use defaults when partial config is provided instead of requiring all options to be specified explicitly #361

Closed
ggrieco-tob opened this issue May 28, 2024 · 0 comments · Fixed by #362

Comments

@ggrieco-tob
Copy link
Member

ggrieco-tob commented May 28, 2024

The removal of the "compilation" section from the medusa config, for instance, the following file:

{
        "fuzzing": {
                "corpusDirectory": "tests/medusa-corpus",
                "deployerAddress": "0x10000",
                "senderAddresses": [
                        "0x10000",
                        "0x20000",
                        "0x30000"
                ],
                "assertionTesting": {
                        "enabled": true
                },
                "propertyTesting": {
                        "enabled": false
                },
                "optimizationTesting": {
                         "enabled": false
                }
        }
}

results in failing to compile any project:

⇾ Reading the configuration file at: min.json
warn Currently, optimization mode's call sequence shrinking is inefficient; this may lead to minor performance issues
⇾ Initializing corpus
⇾ Setting up base chain
error Failed to initialize the test chain
‣ CryticERC20InternalHarness was specified in the target contracts but was not found in the compilation artifacts

The reason for this issue is to have the minimal amount of lines required for showing the use which values they really need, beside the complete default values. This is blocking the merge of crytic/properties#36

@0xalpharush 0xalpharush changed the title Removing the compilation section of the config always results in Failed to initialize the test chain Use defaults when partial config is provided instead of requiring all options to be specified explicitly May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant