-
Notifications
You must be signed in to change notification settings - Fork 24
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
Optional Flag to help Debugging #527
Conversation
Thanks @jmmshn, this is a useful addition. I think this flag could be better as an argument to |
The flag is help with situations where the excution is already serialized like in a fireworks wf.
In my usages cases the second problem seems more annoying since I'm pretty much dealing with a single |
Hi @jmmshn, I'm not sure I follow. What do you mean by "finding the exact I guess one potential benefit of the setting vs argument, is that you could change the setting once a job is already submitted and in the queue (but not running). |
OK, I missed that, you are correct, this will not influence the FW stuff only
Yeah, I think w/e manager we have in the future there might be situations where you add many jobs to a queue and one fails, it will be useful to just rerun the failed job with the flag turned on in some interactive environment and start exploring the stack trace. So even if this only affects the run_locally command for now this can be added to other ways of executing the wf's in the future depending on who you want them to deal with exceptions. I'm OK with either one so I'll leave the decision up to you. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #527 +/- ##
=======================================
Coverage 99.86% 99.86%
=======================================
Files 20 20
Lines 1512 1514 +2
Branches 416 417 +1
=======================================
+ Hits 1510 1512 +2
Misses 2 2
|
OK, I thought about this some more. I think for harder debugging stuff people are gonna be touching the code a lot anyway so it makes more sense to just have it be an argument. |
Thanks @jmmshn |
Optional Flag to help Debugging
Currently, whenever any
run_locally
call fails.The stack trace is produced at the end and we only have access to the error via a logger even
if you set
RAISE_IMMEDIATELY: true
, the stack trace will be provided where the excution actually failed.This allows you to move around better within a debugger.