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
Fix polling mechanism issues #2286
Fix polling mechanism issues #2286
Conversation
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.
small typos, lgtm otherwise
|
||
it('should not throw if a channel is removed from the list', fakeAsync(() => { | ||
raidenServiceSpy.and.returnValues(from([[channel1, channel2], [channel1]])); | ||
const subcription = pollingService.channels().subscribe(); |
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.
subscription
|
||
it('should not show a notification for the same identifier on different network', fakeAsync(() => { | ||
raidenServiceSpy.and.returnValues(from([[channel1, channel1Network2], [channel1Network2]])); | ||
const subcription = pollingService.channels().subscribe(); |
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.
same
This would happen because the the polling mechanism only checked a channels identifier to determine unique channels.
Changes channel identification mechanism to include
token_address
along withchannel_identifier
Add check for newChannel being null when checking for balance changes.
Closes #2282
Closes #2284