-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Investigate "default dodginess" #1990
Comments
Grep the file for the issue number |
There's still a comment for this issue in the codebase, but looks like the test is enabled—is this still an issue? |
Yes it's still an issue: The config system claims that:
Has provided a default |
|
Is there a user-facing consequence to this? I took a brief look at this, and as far as I can tell at least some part of the internals believe that this is the expected behavior - or at least we have code that explicitly tries to make it the case. I.e. the code snippets below go out of their way to make it the case that a Shape config field whose interior fields are all optional gets a default value of If I don't hear back, I'll post a PR that removes the comment and then close this issue. Relevant snippets:
|
Found a comment that indicates a bug in test_system_config.py so creating an issue to track it down.
The text was updated successfully, but these errors were encountered: