-
Notifications
You must be signed in to change notification settings - Fork 133
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
Config when subdag poor error message #188
Labels
triage
label for issues that need to be triaged.
Comments
elijahbenizzy
added a commit
that referenced
this issue
Aug 15, 2023
See #188 for logic. Design is just a simple error message.
elijahbenizzy
added a commit
that referenced
this issue
Aug 15, 2023
See #188 for logic. Design is just a simple error message.
elijahbenizzy
added a commit
that referenced
this issue
Aug 15, 2023
See #188 for logic. Design is just a simple error message.
elijahbenizzy
added a commit
that referenced
this issue
Aug 15, 2023
See #188 for logic. Design is to pass, as the error message will be more helpful later on (when the specified node does not exist)
elijahbenizzy
added a commit
that referenced
this issue
Aug 15, 2023
See #188 for logic. Design is to pass, as the error message will be more helpful later on (when the specified node does not exist)
Fix has been released: https://github.com/DAGWorks-Inc/hamilton/releases/tag/sf-hamilton-1.26.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use
@config
in subdag, and that node doesn't exist but is being requested you'll get a cryptic error.Current behavior
If you are using subdag, and mess up config, you can get this cryptic error.
Stack Traces
Steps to replicate behavior
Run this to get the error
Library & System Information
E.g. python version, hamilton library version, linux, etc.
Expected behavior
There should be a better error here. It's unclear what to do.
The text was updated successfully, but these errors were encountered: