Sean Gillespie b245fd7595 Use both a in-proc and out-of-proc pipenv lock (#2381) ... * Use both a in-proc and out-of-proc pipenv lock Turns out that flock alone is not sufficient to guarantee exclusive access to a resource within a single process. To remedy this, a few FileMutex type wraps both an in-proc mutex and an out-of-proc file-backed mutex to achieve the goal of exclusive access to a resource in both in-proc and out-of-proc scenarios. This commit also uses this lock globally in the integration test framework in order to globally serialize invocations of pipenv install. * Remove merge markers		2019-01-23 09:32:59 -08:00
..
copy.go	Add license headers	2018-05-22 15:02:47 -07:00
lock.go	Use both a in-proc and out-of-proc pipenv lock (#2381)	2019-01-23 09:32:59 -08:00
qname.go	Add license headers	2018-05-22 15:02:47 -07:00
walkup.go	Add license headers	2018-05-22 15:02:47 -07:00