-
Notifications
You must be signed in to change notification settings - Fork 525
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
Paket > 5.4.8 does not work with Klondike 2.0.0 anymore #2504
Comments
Yes paket 5.6 was deleted because of trouble, so very last working version is 5.4.8? |
Yes, |
I think it's #2485 - can you please check these urls? |
@forki yep, that's it. Adding the |
We still haven't looked up the spec, it might be just a bug in https://github.com/themotleyfool/Klondike |
@Kazark Can you open an issue there and link back, maybe they have more insights? |
@forki Thank you! |
@forki I don't think maintaining a list of nuget urls and do what's best for the particular nuget feed is not a sustainable long term solution. I'd argue that we just implement the specs and if there are none we just do what nuget.exe does and get rid of all our performance tricks (it's questionable if they actually yield anything at this time) |
This means we need to open #2472 again? |
that's the problem |
But nuget.exe is working on both I'd assume, so we need to figure out what nuget is doing and do the same... |
I think we should revert my PR and if it s only warning keep it as it is |
Can you please create a pr. Would also need revert my last commit |
@Kazark please retry with latest |
@forki Still not working with 5.6.4, actually. :s |
Just realized that the error looks slightly different now. Here is the new error:
|
https://api.nuget.org/v3-flatcontainer/foo/index.json?semVerLevel=2.0.0 is showing nothing? |
@forki hm, not sure I understand the question; the package that is causing the trouble is only in my local NuGet server. |
oups yes sorry. |
Will do. In a meeting right now but will get back ASAP after that. |
@forki so here's the weird thing. Only the second URL in the bottom block of URLs fails, with a 404. I'm getting 200 on all the others when I run them through a REST client. Confused. |
and the others have correct looking data in it? /cc @matthid |
Let's see. Just grabbed 5.6.6... the first URL returns a 200 with results that appear to be all the versions of the package... |
The second link still fails with 404... |
Oh wait, the second one is only failing because of |
run |
and then |
then outdated again |
nice - yet another issue (but not important now) |
Weird, I really would have thought this was a caching problem on my machine, given that it doesn't seem to be an internal network problem, but after running clear-cache again until it succeeded, I still get the problem. |
Yeah oddly the clear-cache issue seemed to be resolved by running it with --verbose! Or maybe it was just repetition. |
So here's my stderr when I run outdated with --verbose (not included in the log above);
|
ok now it's better. now try the urls. Something is wrong with these urls on your machine (and always run with -f so that you skip the cache) |
|
So if you call "update -f -v" from your machine. Then please check all the
urls. Also the same from vm. There must be a different response somewhere.
Am 12.07.2017 6:53 nachm. schrieb "Keith Pinson" <[email protected]>:
… -f? I haven't been able to find that option. Running with 5.6.10, it has
randomly worked exactly one time so far. However I cannot get it to work
again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2504 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNLsBgrej2kLfgaljuR17tjaNkR9tks5sNPnygaJpZM4OS7uD>
.
|
Okay, I gotta pause for a bit, but will get back to you. |
Ergh, one of my coworkers just saw this now, too. Rats, I was hoping it was enough of a personal problem that I didn't have to be super aggressive about trying to get it fixed. |
@Kazark is there a way to reproduce it on that vm outside of your network? |
Not that I have been able to discover |
I will get back to you with the update -f -v information as soon as I can come up for a breath |
No way, it just happened on the VM when I ran |
Ok. Good. Will try again tomorrow. |
Here is the failure from the VM:
Along with this log (I had redirected stdout):
|
Not wanting to be annoying, just keeping a record of what's going on: another coworker just hit this. |
Yeah. Will take a look tomorrow morning. Hope I can reproduce. |
Okay great. Thanks so much. |
good news: I was able to reproduce with -f param and then easily found the root cause. fix is in paket 5.6.11 the problem was that klondike returns encoded URIs in the OData response. I guess it's actually correct in doing that. But if we just try to follow that link then we get 404. So we actually have to unencode that thing. |
@forki super, thanks for working on this. I will give it a spin. The explanation makes sense. |
Hurrah! Thanks so much. I no longer see the bug. |
heureka! |
Good job guys |
Description
I use two NuGet remotes: an internal NuGet server running Klondike 2.0.0 and nuget.org. Paket versions between 5.5.0 and the latest (5.5.3 currently; I can't get 5.6.0; was it unreleased?) When I went to run
or
paket remove...
then I get an error like:where
Foo
is the name of one of my internal packages andnuget.internal.local
is the name of my Klondike server (actual names differ; these are replaced). This prevents me from using Paket for anything that requires interrogating versions.When I manually run a GET against
http://nuget.internal.local/api/odata/FindPackagesById()?semVerLevel=2.0.0&id='Foo'
, I get results, as always. The Klondike server is up; I can browse it.I have been using Paket with this internal NuGet server for 15 months without any problems, and when I revert to Paket 5.4.8, the issue goes away.
Expected behavior
Still be able to use packages on the Klondike 2.0.0 server.
Actual behavior
Paket errors out on practically anything but
restore
.Known workarounds
Revert back to Paket 5.4.8.
The text was updated successfully, but these errors were encountered: