So this is a weird one... I can't reproduce it on demand but it's now happened at least 4 times.
In working with a workbook (and in these 4 cases they had extracted data and were packaged workbooks), after closing the workbook, the file disappears.
I'm on a Mac.
Data Studio (17.0.7) is running from a partition different then the OS (10.11.6) and my home directory. The extracts are being saved to the default, within the Documents directory I believe, where as the workbooks are being saved to another partition, happens to be the same partition Data Studio is running from.
I originally thought it was something related to saving the workbooks directly to a Google Drive folder so this last time I saved it to another folder (in packaged format), closed the workbook, closed Data Studio and then went and opened that folder to move the workbook to my Google Drive folder and it wasn't there. I re-opened Data Studio and checked Visual Analytics -> Open Recent. It was listed there, and if I left my cursor over it for a second, it displayed the folder that I expected it to be in. I then selected it just to be sure and received the "does not exist" message.
In this case, and the previous occurrence, the workbook was a new one, just created and saved. I believe the two previous cases were similar, new workbooks, but am not 100% sure. I believe in all cases I had closed the workbook but am not sure I had always closed Data Studio. This time I did, other times I don't recollect.
And yes, I'm 100% sure in all 4 of these cases I had saved the workbook... in this case I had made several changes with multiple saves and within that short period of time my backup software had gotten a snapshot of it I was able to pull out. In the previous cases, because I had been saving to my Google Drive I was able to log into Google Drive and recover the file from the online Trash folder. I did check the Mac Trash this time and it wasn't there (but then wasn't expecting it there either).
I checked the datastudio.log file and there are only a couple of complains about bad characters in jar files, doesn't seem to be related to this.
I also can't reproduce it on demand. Watched pot never boils it seems. Nor does this happen on my MBP, just my iMac.
I also checked /var/log/system.log but didn't see any obvious red flags.
Hi Jason,
We'll look into this today & provide an update tomorrow.
@jason: So far we have not been successful in reproducing the issue. Can you email or attach the Aqua Data Studio application logs located in [USER_HOME]/.datastudio/logs
You can email them directly to architect@aquafold.com
By analyzing the logs, we'll be able to tell if an application error is being logged during the save operation.
@jason: So far we have not been successful in reproducing the issue. Can you email or attach the Aqua Data Studio application logs located in [USER_HOME]/.datastudio/logs
You can email them directly to architect@aquafold.com
By analyzing the logs, we'll be able to tell if an application error is being logged during the save operation.
Sent. Not sure it's a save issue as the files are ending up there.. unless Data Studio saves and then if it thinks there is a failure deletes?
Sent. Not sure it's a save issue as the files are ending up there.. unless Data Studio saves and then if it thinks there is a failure deletes?
We've reproduced the issue & are uploading a patch to address it. The scenario can be reproduced as follows:
1) On OS X, launch a new VA workbook, generate an extract (this step is optional), save a packaged workbook (using File > Save) with vizx extension on a different partition (e.g. external hard drive) than the OS partition.
2) The vizx file gets saved successfully.
3) Make changes to the vizx file & save again. ==> The vizx file is deleted & no longer exists on the filesystem
This issue occurs due to a problem w/ Java's File.renameto() method.
We've reproduced the issue & are uploading a patch to address it. The scenario can be reproduced as follows:
1) On OS X, launch a new VA workbook, generate an extract (this step is optional), save a packaged workbook (using File > Save) with vizx extension on a different partition (e.g. external hard drive) than the OS partition.
2) The vizx file gets saved successfully.
3) Make changes to the vizx file & save again. ==> The vizx file is deleted & no longer exists on the filesystem
This issue occurs due to a problem w/ Java's File.renameto() method.
Hi Jason,
Below are the patch download instructions. This patch should address the issue you encountered. In addition, we've added more logging so incase there is a similar failure, the log files will contain additional information & you should get a dialog stating that the save operation failed.
Hi Jason,
Below are the patch download instructions. This patch should address the issue you encountered. In addition, we've added more logging so incase there is a similar failure, the log files will contain additional information & you should get a dialog stating that the save operation failed.
Issue #14758 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 17.0.9-2, 18.0.0-devi-253 |
No time estimate |
Hi Jason,
We'll look into this today & provide an update tomorrow.