-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Better error stacktrace for bad solid definition #1039
Comments
Oh that is very wrong. We should be getting the user stack trace. I will look into this right now.
Sent via Superhuman ( https://sprh.mn/?vip=schrockn@elementl.com )
…On Tue, Mar 26, 2019 at 12:07 PM, Nate Kupp < ***@***.*** > wrote:
As I'm working on a solid, something is wrong with my code. I'm trying to
debug, but this is the unhelpful stack trace I get back from running it:
Execution of event_ingest.transform failed
dagster.core.errors.DagsterExecutionStepExecutionError: Error occured
during step event_ingest.transform File "/ Users/ nate/ src/ dagster/ python_modules/
dagster/ dagster/ core/ execution_plan/ simple_engine. py (
http://users/nate/src/dagster/python_modules/dagster/dagster/core/execution_plan/simple_engine.py
) ", line 217, in _execute_steps_core_loop
_error_check_step_output_values(step_context.step,
step_output_value_iterator) , File "/ Users/ nate/ src/ dagster/ python_modules/
dagster/ dagster/ core/ execution_plan/ simple_engine. py (
http://users/nate/src/dagster/python_modules/dagster/dagster/core/execution_plan/simple_engine.py
) ", line 164, in _error_check_step_output_values for step_output_value in
step_output_values: , File "/ Users/ nate/ src/ dagster/ python_modules/ dagster/
dagster/ core/ execution_plan/ simple_engine. py (
http://users/nate/src/dagster/python_modules/dagster/dagster/core/execution_plan/simple_engine.py
) ", line 315, in _iterate_step_output_values_within_boundary yield
step_output_value , File "/ Users/ nate/. pyenv/ versions/ 3. 6. 8/ lib/ python3.
6/ contextlib. py (
http://users/nate/.pyenv/versions/3.6.8/lib/python3.6/contextlib.py ) ",
line 99, in __exit__ self.gen.throw(type, value, traceback) , File "/ Users/
nate/ src/ dagster/ python_modules/ dagster/ dagster/ core/ execution_plan/
simple_engine. py (
http://users/nate/src/dagster/python_modules/dagster/dagster/core/execution_plan/simple_engine.py
) ", line 341, in _execution_step_error_boundary e, , File "/ Users/ nate/
. pyenv/ versions/ 3. 6. 8/ envs/ dagster-3. 6. 8/ lib/ python3. 6/ site-packages/
future/ utils/ __init__. py (
http://users/nate/.pyenv/versions/3.6.8/envs/dagster-3.6.8/lib/python3.6/site-packages/future/utils/__init__.py
) ", line 398, in raise_from exec(execstr, myglobals, mylocals) , File
"<string>", line 1, in <module>```
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (
#1039 ) , or mute the thread (
https://github.com/notifications/unsubscribe-auth/AbaFeRJv7EZzglHYhNHCQZ2bxV4Y06rEks5vam_dgaJpZM4cMO80
).
|
schrockn
added a commit
that referenced
this issue
Mar 26, 2019
Addresses #1039 and adds test to catch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I'm working on a solid, something is wrong with my code. I'm trying to debug, but this is the unhelpful stack trace I get back from running it:
The text was updated successfully, but these errors were encountered: