-
Notifications
You must be signed in to change notification settings - Fork 540
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
Unable to create or update lock file for project when project directory is missing from cache #578
Comments
This was done using 0.12.0 release on both machines. |
Oh, and since more changes have gone to master since opening this issue, to help reproducibility, all of this was done with |
I'm seeing this same issue with updating dependencies with
When I looked in the |
@kujenga I'm seeing the same, no |
I'm on Mac OS X 10.11.6 I just found that I was able to resolve the issue by running |
I do the majority of my development on Windows and am working on another project which imports this one, so that would make sense why it worked there. After doing a |
running into this too. i'm baffled why glide thinks that it needs to put the package itself into glide.lock..... |
I'm seeing some additional strange behavior that seems related to this. Here are the steps I'm going through. Let's say I'm in repo Run from within
From this point, there are two options I tried. The first was just running The next thing I tried, which got me up and running, was directly after the initial |
Hey folks, sorry for the slow response. I was at a conference with limited connectivity and then traveling with no connectivity over the weekend. I understand the frustration at this issue. I have a feeling there are a couple things going on here. First, an element in the cache may be corrupt. You can clear the cache with Second, and error like:
Usually means the version for the repo has been set to one that doesn't have a subpackage. That there are incompatible changes that occurred. I didn't imagine this coming along with a corrupt cache. |
@mischief Glide has trouble with putting the package itself into the |
|
Thanks @mattfarina for the response! I'm seeing the same behavior that @jrick just posted after following those steps. My feeling is that there isn't any corruption of elements in the cache here, the actual error thats printed is a result of not handling the case where an element in the cache is totally missing, when it's looking for something from the current repo in the cache. Still, I think this is the manifestation of the problem rather than the root of it. In the example posted by @jrick above, do you have a sense of why it's even looking in the cache for packages that are within the current repo? Shouldn't it just let the local ones be used? My impression was that this is occurring when a dependency of the current repo depends on the current repo, something like A -> B -> A. In my mind, the expected behavior would be for the current repository to never be vendored within itself. |
Oh, Oh, Oh, PR coming. |
Can y'all please test the PR at #588? I think this fixes it. |
Fixed #578: Not resolving parent project packages in some cases
glide install |
Hi @mattfarina, |
I'm seeing an issue trying to update dependencies for
github.com/decred/dcrd
whenglide update
is run from bitrig (an openbsd fork):It also seems impossible to
update
even when an entirely new glide.yaml is created fromglide init
:The same project can be successfully updated on Windows, and produces the following lockfile:
(Sidenote: Why did it list the project itself in the lockfile?)
I've gone through all dependencies in the vendor directory on Windows where the update succeeded, and did not find any other projects that included a glide.yaml, so those error messages about unsatisified version requirements don't make much sense in this case.
The text was updated successfully, but these errors were encountered: