Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Failed/incomplete downloads still appear in local data sources #375

Closed
forman opened this issue Sep 20, 2017 · 4 comments
Closed

Failed/incomplete downloads still appear in local data sources #375

forman opened this issue Sep 20, 2017 · 4 comments
Assignees
Milestone

Comments

@forman
Copy link
Member

forman commented Sep 20, 2017

Expected behavior

Just got a connection timeout during a download of a large data source (the OZONE one from #374). I expected the failed/incomplete download not to appear in my local data sources next time I start Cate.

Actual behavior

The data source appears.

image

Note that the *.lock* file could tell that a download is ongoing. It could also contain status incl. progress and error information about the download.

The issue is closely related to #337.

Specifications

Cate 0.9.0.dev7

@forman forman added this to the IPM6 milestone Sep 20, 2017
@forman forman modified the milestones: IPM6, 1.0 Sep 21, 2017
kbernat pushed a commit that referenced this issue Sep 22, 2017
kbernat pushed a commit that referenced this issue Sep 22, 2017
kbernat pushed a commit that referenced this issue Sep 22, 2017
kbernat pushed a commit that referenced this issue Sep 26, 2017
kbernat pushed a commit that referenced this issue Sep 26, 2017
kbernat pushed a commit that referenced this issue Sep 26, 2017
kbernat pushed a commit that referenced this issue Sep 26, 2017
@mzuehlke
Copy link
Collaborator

Hi @kbernat

When the user cancels the download you remove all files, but if an error occurs while downloading all files already downloaded remain on disk. Is this intended?

cate/cate/ds/esa_cci_odp.py

Lines 1009 to 1017 in b519f21

try:
self._make_local(local_ds, time_range, region, var_names, monitor=monitor)
except Cancellation as c:
local_store.remove_data_source(local_ds)
raise c
except Exception as e:
if local_ds.is_empty:
local_store.remove_data_source(local_ds)
raise e

@kbernat
Copy link
Collaborator

kbernat commented Sep 26, 2017

@mzuehlke yes, it's our "resume" feature :)

@kbernat
Copy link
Collaborator

kbernat commented Sep 26, 2017

@mzuehlke we may think about asking user if incomplete data should be kept or not..

@forman
Copy link
Member Author

forman commented Sep 26, 2017

I suggest that a resume should only be possible/required on external errors, e.g. timeout and IOError, not on any (possibly developer) error that might occur in make_local, see #393

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants