Skip to content
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

Debugger #2

Open
thinkerbot opened this issue Jun 15, 2009 · 0 comments
Open

Debugger #2

thinkerbot opened this issue Jun 15, 2009 · 0 comments

Comments

@thinkerbot
Copy link
Owner

Signatures

No problem to determine incorrect node signatures at the call, process, and process_block levels. The output should notify the node, and ideally the join causing the problem. Once a trace is in place, the join could be found by searching back in the trace for the specified inputs:

trace.reverse_each
  if node.joins has the present task
  and the inputs come from the join (match object, or find object in an array)
  then consider the join found (or search everything... maybe the issue is upstream?)

And once you have the join, help can be provided to suggest what needs to be done to fix the error.

Replay

A breakpoint could be added to step through the workflow. In this case, or perhaps generally, the trace should be saved to disk allowing quick replay. Will not work with objects that cannot be serialized, and that's ok. Simply encourages people not to pass around IO or blocks, or to fix YAML.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant