[Bug] Saves deleted after updating from 2.3.1 to 2.4.0

[Pilotiju]

🐛 Description

After restarting the extension to update it from version 2.3.1 to 2.4.0, all the stats from before (code time, languages, project time... from version 2.3.1) didn't show up, as if it was my first time using that extension. Every stat got reset.

ℹ️ Extra Information

In my folder Users\[user_name]\.vscode\extensions there are multiple statice folders. There is devpotatoes.statice-2.3.1, devpotatoes.statice-2.4.0 and .42d⬛87⬛-6⬛81-⬛7⬛b-⬛7⬛⬛-d7⬛⬛46⬛0⬛b⬛2 (I blacked out most of the numbers/letters since I am not sure if that folder name holds any sensitive information). The folder .42d⬛87⬛-6⬛81-⬛7⬛b-⬛7⬛⬛-d7⬛⬛46⬛0⬛b⬛2 seems to be similar, if not the same, as the folder devpotatoes.statice-2.4.0 but without the data folder. It was installed/downloaded about 30 minutes earlier than the folder devpotatoes.statice-2.4.0.

The (old) backups are still in the folder devpotatoes.statice-2.3.1 and after copying them to the backups folder in devpotatoes.statice-2.4.0 and restoring the backups, the old stats reappear again.

💻 VS Code Version

• 1.104.3

🖥️ Operating System

• Windows 10

[devpotatoes]

Hey, thanks a lot for reporting this bug too.
I'm glad to hear that copying the backups from the old 2.3.1 folder to 2.4.0 worked, that's exactly the right workaround for now. You can also use the export/import interface from your account menu as an alternative.

One of my friends has already reported this issue to me, but to be honest, I don't have this bug on my side yet.
Still, I will work on making this process smoother in future updates so that stats are preserved automatically during updates.

Also, from what I have read, those duplicate or ID named folders are temporary folders created by VS Code during installation or updates of the extension. And seems to be part of its normal update process.

Thanks again for taking the time to describe everything in detail, it really helps a lot !

[Pilotiju]

I believe that the stats do not show up because every time the extension gets updated, a new folder in Users\[user_name]\.vscode\extensions gets created (the newer version), and the old one gets deleted. The data/stats are probably stored in the old folder, which is not used anymore/deleted.

A workaround could be to have another folder somewhere that stores only the data for statice (maybe even let the user locate the folder they want their data to be stored in), without getting deleted/replaced/overwritten.

To recreate that bug, you could use a Virtual Machine (VM or sandbox) on your computer. As you probably know, a Virtual Machine acts like a new and empty computer inside your actual computer.

Here is how I recreated the bug in a VM

1. Install VS Code in the VM
2. Search statice in the Extensions tab
3. Select your extension and click on the gear (next to the checkbox with Auto Update)
4. Select Install Specific Version...
5. Choose an older version (for example 2.3.1)
6. Disable Auto Update
7. Get some coding time/stats/data of course
8. Close VS Code and open it again
9. In the Extensions tab should be a notification
10. Click on the Extensions tab and update statice
11. Click on Restart Extension
12. Now if you open up your Dashboard again, the stats are missing

Keep in mind to install the extension the way a normal user would install it, not how the developer would/is capable of (which is probably why you did not have the bug, but your friend and I did).

Question

What is the Import and Export feature meant for? As far as I know they serve a very similar function like the backups, but manually. As far as I understand, is Import stats the same as Restore backup but with .statice files instead of .gz files.