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
When generating an invoice for an asset held in an asset channel, if the rfq process fails, due to non-responsiveness of the peer, incorrect config, etc., the tapd process crashes and litd needs to be restarted. Doesn’t seem to happen when there is no rfq config and the [litcli] peer [peer pub key] sent back an invalid quote, status: PRICE_ORACLE_QUERY_ERR
error is returned. But it does happen when the process times out and this error is received, [litcli] error adding sell order: rpc error: code = Unknown desc = timeout waiting for response from peer
the tapd process then fails with this error visible in the output of $ litcli status "error": "received critical error from sub-server (taproot-assets), shutting down: failed to handle outgoing message: error sending outgoing message to stream handler: unable to send message to peer: rpc error: code = NotFound desc = peer is not connected",
My environment
I’m on the v0.13.99-alpha.rc3 release of litd on a Ubuntu machine.
Steps to reproduce
Check that everything is up and running.
$ litcli status
Attempt to create an asset based invoice in a situation where it will fail… other node is down, config is incorrect, etc.
$ litcli --network=testnet --macaroonpath=~/.lnd/data/chain/bitcoin/testnet/admin.macaroon ln addinvoice --asset_id [asset id] --asset_amount 100
Check on that status of tapd
$ litcli status
Expected behavior
The invoice creation cli command will return error message but litd and tapd will continue running.
Actual behavior
The invoice creation cli command returns an error message and litd stays running, but tapd fails.
Attached are logs from a tapd crash after a failed invoice creation. lndJulRFQCrash.log
The text was updated successfully, but these errors were encountered:
Fixes#1010.
With this commit we introduce a new fn.CriticalError type and only send
RFQ errors to the main error channel (which causes the daemon to shut
down) if an error is critical to the operation and can't just be logged.
The Issue
When generating an invoice for an asset held in an asset channel, if the rfq process fails, due to non-responsiveness of the peer, incorrect config, etc., the tapd process crashes and litd needs to be restarted. Doesn’t seem to happen when there is no rfq config and the
[litcli] peer [peer pub key] sent back an invalid quote, status: PRICE_ORACLE_QUERY_ERR
error is returned. But it does happen when the process times out and this error is received,
[litcli] error adding sell order: rpc error: code = Unknown desc = timeout waiting for response from peer
the tapd process then fails with this error visible in the output of $ litcli status
"error": "received critical error from sub-server (taproot-assets), shutting down: failed to handle outgoing message: error sending outgoing message to stream handler: unable to send message to peer: rpc error: code = NotFound desc = peer is not connected",
My environment
I’m on the v0.13.99-alpha.rc3 release of litd on a Ubuntu machine.
Steps to reproduce
Check that everything is up and running.
$ litcli status
Attempt to create an asset based invoice in a situation where it will fail… other node is down, config is incorrect, etc.
$ litcli --network=testnet --macaroonpath=~/.lnd/data/chain/bitcoin/testnet/admin.macaroon ln addinvoice --asset_id [asset id] --asset_amount 100
Check on that status of tapd
$ litcli status
Expected behavior
The invoice creation cli command will return error message but litd and tapd will continue running.
Actual behavior
The invoice creation cli command returns an error message and litd stays running, but tapd fails.
Attached are logs from a tapd crash after a failed invoice creation.
lndJulRFQCrash.log
The text was updated successfully, but these errors were encountered: