lock the repository if update / download running

[julianhille]

The repository should be locked while updating so that not two concurrent processes do not change it at the same time.

[JustinCappos]

This is something we are leaving up to the repository developers. Yes,
this needs to happen, just like one needs to serve content in some way
(e.g., using HTTP or FTP). We don't prescribe a specific way to do this
and leave it up to the repository implementers.

On Mon, Aug 29, 2016 at 12:09 PM, Julian Hille notifications@github.com
wrote:

The repository should be locked while updating so that not two concurrent
processes do not change it at the same time.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#369, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0XD_hcEWzlqmBYvDXGOJpXumeG4JtHks5qkwQvgaJpZM4Jvoam
.

[julianhille]

I thought it would just be very easy to add a flock to "the_repository_dir/.lock" with an configurable time_delta when to reclaim the lock if a process before may have been killed or cancelled and the flock file still exists.

[julianhille]

At least we should add a note to the readme that concurrent processes may harm the repo and that the lock is up to the repository maintainer?

Just for completeness im talking about the update client :>

[JustinCappos]

Ah, sure. We should update the docs in both the client and repository to make this clear.

@vladimir-v-diaz: can you take a look at this and ensure this is clear?

[trishankatdatadog]

This is connected to #49

[mnm678]

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