You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Faucet is currently configured to use tap-parser version 0.4.0. The latest version is 1.2.2, but faucet has several compatibility issues with it.
I can get it to run without crashing if I change res.number to res.id in the assert event handler, but the output is all messed up.
I discovered this in the process of investigating why faucet wasn't properly handing my TAP "Bail out!" notice. The reason is that it uses a tap-parser that does not emit bailout.
The text was updated successfully, but these errors were encountered:
I now see why you never upgraded faucet to the latest tap-parser. I have written a faucet-like runner for tap. It's called subtap. I had to reconstruct all the found/wanted value differences from the new event output. Lots of work!
Faucet is currently configured to use
tap-parser
version 0.4.0. The latest version is 1.2.2, but faucet has several compatibility issues with it.I can get it to run without crashing if I change
res.number
tores.id
in theassert
event handler, but the output is all messed up.I discovered this in the process of investigating why
faucet
wasn't properly handing my TAP "Bail out!" notice. The reason is that it uses atap-parser
that does not emitbailout
.The text was updated successfully, but these errors were encountered: