-
Notifications
You must be signed in to change notification settings - Fork 378
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
Treat trying to deposit on a closed channel as recoverable error #4693
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -189,6 +189,10 @@ class DuplicatedChannelError(RaidenRecoverableError): | |
"""Raised if someone tries to create a channel that already exists.""" | ||
|
||
|
||
class ChannelNotOpenError(RaidenRecoverableError): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nitpick: I would generalize this to something like There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmmm perhaps unexpected channel state? Invalid would mean that it's something which we can't even parse. |
||
"""Raised if someone tries to work on a channel that is no longer in an open state.""" | ||
|
||
|
||
class ContractCodeMismatch(RaidenError): | ||
"""Raised if the onchain code of the contract differs.""" | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about handling it here. Since this is right after opening in the same function I don't see how a race with the channel being closed can happen here.
But I opted to handle it here too just to be safe.