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

Open trade data lost upon update #5019

Closed
huey735 opened this issue Dec 29, 2020 · 7 comments
Closed

Open trade data lost upon update #5019

huey735 opened this issue Dec 29, 2020 · 7 comments
Labels

Comments

@huey735
Copy link
Member

huey735 commented Dec 29, 2020

Description

Upon update, trade data was lost. We can still see the transactions under the Funds > Transactions tab but they're not interpreted as trade transactions - "Taker and tx fee:" or "Multisig deposit" - and are instead labelled as simple "Withdrawn from wallet" or "Miner fee for BSQ tx".

Version

Update from 1.5.1 to 1.5.2

Screenshots

In this case the trader was the Taker on all trades. The transactions are colored in pair by their trade.

BTCSellerTaker-transactions-edited

Device or machine

Mac OS Big Sur 11.1

Additional info

The trader had other open trades that seem unaffected by this issue.

@ripcurlx ripcurlx added the a:bug label Dec 29, 2020
@ripcurlx
Copy link
Member

@sqrrm @chimp1984 Can it be that this was caused by the v1.5.2 update?

@chimp1984
Copy link
Contributor

@huey735 Can you check if there is a corrupted files folder in the data directory (in the db folder)? seems one of the db files got corrupted.

@huey735
Copy link
Member Author

huey735 commented Jan 25, 2021

@chimp1984 Do you want me to ask them for their db/ folder?

@chimp1984
Copy link
Contributor

They can have themself a look into the db folder if there is any corrupted_files sub folder

@cd2357
Copy link
Contributor

cd2357 commented Mar 29, 2021

@huey735 any updates? Investigation ongoing, or can this be closed? Thanks.

@huey735
Copy link
Member Author

huey735 commented Mar 30, 2021

@cd2357 I think it has been fixed by #5280
@jmacxx @chimp1984 am I right?

@jmacxx
Copy link
Contributor

jmacxx commented Mar 30, 2021

Correct, fixed by #5280 👍

@cd2357 cd2357 closed this as completed Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants