Skip to content
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

Uncheck selected trades #3287

Closed
yabirgb opened this issue Aug 3, 2021 · 4 comments
Closed

Uncheck selected trades #3287

yabirgb opened this issue Aug 3, 2021 · 4 comments
Assignees
Labels
backend bug Something isn't working
Milestone

Comments

@yabirgb
Copy link
Member

yabirgb commented Aug 3, 2021

Problem Definition

When you click on the button to select all the trades you can't unselect them all at once by clicking the same button (not other that I've seen)

image

Operating system: Docker
Rotki version: 1.19.1

@yabirgb yabirgb added bug Something isn't working frontend labels Aug 3, 2021
@LefterisJP
Copy link
Member

So this is for @kelsos to look at I guess

@kelsos
Copy link
Member

kelsos commented Aug 3, 2021

What was the state of the application when that happened. If I remember correctly, the way I implemented the select functionality, it only selects items based on the visible dataset. If you select all while it is loading for example and then more entries appear then the checkbox would be unchecked because the newly added items are not selected.

The same would happen if you select a location filter and then remove the filter.

@LefterisJP LefterisJP added this to the v1.20.0 milestone Aug 3, 2021
@yabirgb
Copy link
Member Author

yabirgb commented Aug 3, 2021

@kelsos There was nothing selected, everything loaded already and no filter was applied

@LefterisJP LefterisJP changed the title Uncheck selected tradres Uncheck selected trades Aug 4, 2021
@LefterisJP
Copy link
Member

So I managed to reproduce it and then with the help of @kelsos figured out the problem is actually the backend generating the same identifier for two different trades.

This, at least in my case, happened for different swaps from different AMMs but in the same transaction. So using an aggregator like paraswap or 1inch and having same transaction hash for a balancer swap and a uniswap swap.

I can easily fix by using the log index in the trade id too. But we probably need a nice way to log this in the frontend in case this happens again, so we know what is the root cause and fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants