-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
feat: add default yaml config #1157
Conversation
|
# alchemy: | ||
# min_retry_delay: 1_000 # 1 second delay on fail | ||
# retry_backoff_factor: 2 # explonential backoff | ||
# max_retry_delay: 30_000 # 30 seconds | ||
# max_retries: 3 | ||
# retry_jitter: 250 # 250 milliseconds |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
like this @fubuloubu? 😉 (re: getting provider settings from Config)
This pull request is considered stale because it has been open 30 days with no activity. Remove stale label, add a comment, or make a new commit, otherwise this PR will be closed in 5 days. |
This PR was closed because it has been inactive for 35 days. |
What I did
attempt to pull out all the defaults from code into a single yaml
Why I did it
this can be used to transparently add more detailed parameters, like in ApeWorX/ape-alchemy#35. also allows non-coder users to understand what the default settings are, and to easily override them.
How I did it
removed parameters and hard-coded them into the standard yaml. maybe a separate
default-config.yaml
would be better thanape-config.yaml
.replaced the context-based test_config with an overload to the default config that executes additional overrides (I bet this is causing lots of test failures):
= 195 failed, 512 passed, 3 skipped, 7 xfailed, 15 warnings, 31 errors in 1125.89s (0:18:45) =
How to verify it
possibly additional tests should be needed, though i got it working with test_config.py
Checklist
default-config.yaml
, distinct fromape-config.yaml