"Permission denied" error when downloading dataset using GUI

[HelenClifton]

Expected behavior

Downloading a subset of esacci.SST.day.L4.SSTdepth.multi-sensor.multi-platform.OSTIA.1-1.r1

Actual behavior

The download failed soon after starting.
Following errors were displayed:

Note

It's a similar problem to #257 which was seen when downloading same dataset with same constraints using the CLI. @HerzogStephan
I think this problem is different - with CLI you can download the dataset but not open it, but with GUI you cannot download. The error messages displayed are also different.

Steps to reproduce the problem

1. Select data store: ESA CCI Open Data Portal
   Highlight data source: esacci.SST.day.L4.SSTdepth.multi-sensor.multi-platform.OSTIA.1-1.r1
   Click on “Download and/or open remote dataset”

2. In “Download Data Source” window:
   • Select Time Constraint and enter start time of 1997-12-01 and end time of 1998-12-31

• Select Region Constraint, enter:
o Lon. from: -175
o Lon. to: -115
o Lat. from: -10
o Lat. to: 10

• Select Variables Constraint, select variables analysed_sst and analysis_error from the list

• Select “Download and make local data source“ and enter Unique identifier esacci.SST.day.L4.SSTdepth.multi-sensor.multi-platform.OSTIA.1-1.r1_19971201_19981231_reg-175_-10_-115_10_var_analysed_sst followed by a SPACE character

• Ensure “Open dataset from local data source“ is unselected.

• Click on “Download”

Specifications

cate 0.9.0-dev5
Windows 7 Professional

[HelenClifton]

More information @forman @kbernat : It looks like there was a space at the end of the unique ID name and this is what caused the problem.
When I tried again, and made sure there was no space at the end, the download started successfully.

[forman]

Just verified. It definitely comes from xarray o Windows when writing to a files that has already been opened for reading.

[kbernat]

We upgraded xarray in the meantime and nobody reported it again. We can close it for now.

[kbernat]

I will try to reproduce it anyway...

[HelenClifton]

@forman @kbernat It does still happen with cate-2.0.0-dev.2
But only when there is a space accidently added at the end of the unique ID name
The error is now:

Traceback:
Traceback.txt

[HelenClifton]

@forman Still happening in cate-2.0.0-dev.7

Traceback.txt

[kbernat]

@HelenClifton i will take care of it

[HelenClifton]

@kbernat Thanks, see traceback above

[HelenClifton]

@papesci Confirmed that error is still happening with cate-2.0.0-dev.9

[papesci]

@HelenClifton i can't reproduce the issue with cate-2.0.0-dev20. It have been fixed from cate-2.0.0-dev18. Can you confirm ?

[HelenClifton]

Hi @papesci Tested with cate-2.0.0-dev.20 (Windows) but still seeing it
The problem happens when there is a SPACE character at the end of the local ID name (see updated "steps to reproduce" above

[papesci]

In principle no space or other symbols should be allowed to be used for local dataset names. The behavior between window and Linux OS is different also in this case. To avoid inconsistency a check to the dataset name has been added, only letters, numbers and underscore are now allowed to be used. An exception is raised in case the ds name is not compliant with the naming rule. Branch 343

[HelenClifton]

@papesci @forman Confirmed fixed in dev.23 - thanks !