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

Generated resource names not always unique #391

Closed
forman opened this issue Sep 22, 2017 · 3 comments
Closed

Generated resource names not always unique #391

forman opened this issue Sep 22, 2017 · 3 comments
Assignees
Milestone

Comments

@forman
Copy link
Member

forman commented Sep 22, 2017

Expected behavior

Generated resource names shall always be unique within a workspace.

Actual behavior

A newly generated resource name will be the same as a previous one while others task that bind resources haven't finished yet and new

  • operation steps are created or
  • data sources are downloaded/opened

This is the reason for #306 and hence will fix it.
This issue is accompanying #369 in the case where no resource name was provided by the user.

Steps to reproduce the problem

  1. Open dataset that takes some time i.e. requiring a download or OPeNDAP
  2. While opening run operation or open data source

Specifications

Cate 0.9.0.dev7

@forman forman added this to the 1.0 milestone Sep 22, 2017
@forman forman self-assigned this Sep 22, 2017
@forman
Copy link
Member Author

forman commented Sep 24, 2017

@forman
Copy link
Member Author

forman commented Sep 27, 2017

Reopened because of #306

@forman forman reopened this Sep 27, 2017
@forman
Copy link
Member Author

forman commented Sep 27, 2017

Implementing this correctly requires resolution of #26.

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

1 participant