Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure thread-safety #49

Closed
trishankkarthik opened this issue Mar 19, 2013 · 4 comments
Closed

Ensure thread-safety #49

trishankkarthik opened this issue Mar 19, 2013 · 4 comments
Assignees

Comments

@trishankkarthik
Copy link
Contributor

Presently, there is no thread-safety for some important things, such as:

  • Switching tuf.conf global configuration variables between different TUF clients.
  • Downloading the same target files with the same TUF client.
@JustinCappos
Copy link
Member

I vote for a global lock for expediency.

On Tue, Mar 19, 2013 at 2:17 AM, TKK notifications@github.com wrote:

Presently, there is no thread-safety for some important things, such as:

  • Switching tuf.conf global configuration variables between different
    TUF clients.
  • Downloading the same target files with the same TUF client.


Reply to this email directly or view it on GitHubhttps://github.com/akonst/tuf/issues/49
.

@trishankkarthik
Copy link
Contributor Author

I wonder whether we would like to extend concurrence-safety to the repository tools (e.g. making a delegation).

Why would we want this? Well, suppose a developer wants to generate TUF metadata for tens of thousands of packages. It would be nice if she could parallelize her automation without worrying about whether the TUF repository tools would be concurrence-safe (e.g. ensuring that the parent/delegator metadata is safely updated).

Anyway, even if we wanted to do this, it would be at the end of our priority queue.

@lukpueh
Copy link
Member

lukpueh commented Dec 16, 2019

Quick fix: Note in the readme that TUF might behave unexpectedly when concurrently downloading from the same location to the same location.

@mnm678
Copy link
Contributor

mnm678 commented Jan 7, 2020

#972 added an explanation of this limitation to the readme.

@mnm678 mnm678 closed this as completed Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants