Empty Error when Accepting Offline Order Leaves Order Broken

[jjeffryes]

An IPFS rebase node made an offline order to a 2.3 node.

When the 2.3 node was started, it detected the order and attempted to accept it (ob/orderconfirmation).

The client showed an empty error, which usually means a status of 500 was returned with no data. I didn't have the dev console up when this happened to see what the exact result was.

When I retried accepting the order with the dev console active, the error became "reason": "No unspent transactions found to fund order".

The order is now stuck in that state.

[jjeffryes]

I was able to reject the order.

[jjeffryes]

Attempting to cancel the same order from the buyer's side after the seller had rejected it, but before the order was updated on the buyer's machine (calling ob/ordercancel) resulted in a 500 error with "reason": "exhausted maximum attempts for request"

[jjeffryes]

Cancelling a new offline order between the same two nodes worked normally.

Attempting a new offline order between the same two nodes resulted in "reason": "No unspent transactions found to fund order" on the first attempt to accept the order.