-
Notifications
You must be signed in to change notification settings - Fork 3
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
plugin.sendData is not a function #7
Comments
Could you run |
ilp-plugin creating plugin with module ilp-plugin-xrp-escrow +0ms
ilp-curl loading file example.txt +0ms
ilp-curl running +1ms
ilp-plugin-xrp-escrow connecting to api +0ms
ilp-plugin-xrp-escrow subscribing to account notifications for
r3765xnYfmQbDfqkdrG3B58gCshogYdziM +756ms
ilp-plugin-xrp-escrow connected +215ms
ilp-curl connected +971ms
ilp-fetch:info attempting http request. url=https://unhash.ilp-test.com
+0ms
ilp-fetch:trace parsed `Pay` header. method=interledger-psk2 +0ms
ilp-fetch:trace using PSK2 handler. +0ms
ilp-fetch:trace connecting plugin +0ms
ilp-plugin-xrp-escrow connecting to api +404ms
ilp-plugin-xrp-escrow subscribing to account notifications for
r3765xnYfmQbDfqkdrG3B58gCshogYdziM +0ms
ilp-plugin-xrp-escrow connected +175ms
ilp-fetch:trace calling handler. +175ms
ilp-fetch:psk2 quoting destination amount via psk2. amount=70
account=test.amundsen.bmp.btp18q1xrp.niIEYxdoZr2xzlvHNCI9UOsa6dXAenCqIalZZDXMS-o.local.-lxQzp6X398AzoPHLPHuiVuhmsLFVWimWnCX4pz_Gw8.fmktGsNgtW5AFgPs8gRVmUUV
+0ms
ilp-psk2:sendRequest using user-specified unfulfillable condition for
request: 3416586447 +0ms
ilp-psk2:sendRequest sending request 3416586447 for amount: 1000 +1ms
plugin.sendData is not a function
|
Looks like the problem is definitely that
|
npm ls -g ilp-plugin-xrp-escrow:
/usr/lib
└── ilp-plugin-xrp-escrow@1.0.5
No linked packages
echo $ILP_PLUGIN:
ilp-plugin-xrp-escrow
thank you
|
unsetting |
Hi,
I'm running moneyd on the testnet and when I run ilp-curl -X POST https://unhash.ilp-test.com --data @example.txt - I get plugin.sendData is not a function. This looks like perhaps a node version or node package version issue... Any suggestions before I start trial and error package debugging?
The text was updated successfully, but these errors were encountered: