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
To help us more easily debug your issue please check the boxes for which requirements for safe usage or Raiden were followed:
The Ethereum node was always up to date with the chain tip and never stopped running.
No Ethereum transaction was sent for the account that Raiden manages by another app.
The Ethereum account used by Raiden always had sufficient ETH.
The Raiden DB that exists by default at ~/.raiden was never altered or deleted.
The Raiden node was never restarted. If yes please provide more info.
The ethereum node was not switched while Raiden was running.
The Raiden REST API is protected from public access.
Settled channels are shown as opened in list channels API (GET api/v1/channels).
Steps to reproduce:
Open a channel in any token network
Close a channel and wait for it to settle
Restart raiden node
Retrieve a list of open channels from the node
Whats even worse, if I try to close this channel again using webui or API the raiden node will crash (raiden.exceptions.RaidenUnrecoverableError: The channel was not open at the provided block (0xcf07c12f24201113c376f22702fc60e382336bbc10a66caa5679e4286d54b1c5). This call should never have been attempted.
and everything worked so far - the transactions were successful on the blockchain.
Then the Raiden Client was restarted (or started) and fetched all the blockchain events. Because Ropsten is not used for Raiden there are not so many events. So the Raiden Clients decode and dispatch all events in batches and not interleaved. However, the decoding logic for the channel close depends on the dispatch of the channel open.
We will now decode and dispatch per item instead of batch-wise.