commit | fe39e19b52a0b7078167d9b942ce446095b640ca | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 18:32:21 2016 -0400 |
committer | Nick M. Mitchell <nickm@us.ibm.com> | Mon Oct 03 18:32:21 2016 -0400 |
tree | e9abf471022b0913d40e49cbb353520af35a2313 | |
parent | 041aac5bb53a3259f3a54611f93bd778bda53e96 [diff] |
update repl to handle blank lines
This project currently supports debugging NodeJS actions on your laptop.
Start the debug client:
% (cd client; ./wskdb) Welcome to the OpenWhisk Debugger ? (wskdb)
You will now be in a REPL. Issue help
to see the list of available commands.
The syntax here is almost identical to that of the wsk
CLI.
? (wskdb) invoke actionName -p param1 value1 -p param2 value2
If you haven‘t yet attached to the action you are invoking, the invocation will proceed as if you weren’t in the debugger, and had issued a blocking invocation from the CLI.
Say for example you wish to attach to an action foo
, and this action occurs in a sequence seq
.
? (wskdb) attach foo Attaching to foo Creating action trampoline Creating sequence splice seq
If you wish to limit the instrumentation to the action, avoiding any containing rules or sequences:
? (wskdb) attach foo --action-only Attaching to foo Creating action trampoline