-
Notifications
You must be signed in to change notification settings - Fork 527
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
Issue with paket convert-from-nuget #1225
Comments
(side note: @mrinaldi @theimowski this is the third time I see |
What nuget server are you using? |
ProGet 3.4.3 (Build 7) Yes, the other bugs I have reported the last few days uses the same server |
Mhm. Seems like it's waiting in the cache method /cc @xavierzwirtz Can you try to downgrade paket to maybe 3 or 4 minor versions? |
No I meant something like 2.21 |
I hate when things go wrong on private feeds... |
Ok. Seems it's not related to latest cache changes. Unfortunately the attached debugger info is not that helpful. What I usually do in this situation is to start the convert process from VS
|
it's also possible that it is reated to |
one thing you could do is to run |
Internal Server Error from nuget server when calling this uri "http://dips-nuget/nuget/TeamFrost/Packages?$filter=Id eq 'odp.net.managed' and NormalizedVersion eq '121.1.2'" |
do you get the same error manually from browser? |
Yes, trying do find error logs from server |
/cc @gdivis |
Regarding the |
I'm on the |
Mhm that sounds like it could be the issue. If I just could reproduce it.
|
Shouldn't Paket fail with an error message instead of freezing when the http call to our local nuget repo fails? |
Yes. The code you mentioned is part of the normal paket update command.
|
I left it yesterday and 8 hours later it still waits. I've tried to get error logs from the server but all i could find was iis
|
I will add a timeout to that function. |
what about this url? http://dips-nuget/nuget/TeamFrost/Packages?$filter=Id eq 'odp.net.managed' and Version eq '121.1.2' does this work in browser? |
there is a new alpha version that you can test. It runs all Nuget protocols for "GetPackageVersion" in parallel. Maybe it improves things. |
This doesn't work:
|
I'll test the code later today |
Freezez after this output Did a paket.bootstrapper.exe prerelease before paket convert-from-nuget -v -f
|
OK so Async.Chice didn't work. Sorry for the pingpong (always big fun with private networks). I need to take a look at the code. At the moment I have no idea without debugging it. |
So I have played a little with our ProGet Nuget server and the query that Paket runs. If you just but each part of the filter statement inside a () then it works Change
to
|
Ok. Not sure if this is a proget bug, but we can do that. /cc @maartenba do you see issues with this change in regard to other servers like myget? |
It's valid OData so should work fine |
this works for nuget as well https://www.nuget.org/api/v2/Packages?$filter=(Id eq 'odp.net.managed') and (Version eq '121.1.2') |
ok then let's do it. Thanks maarten. |
@theggelund could you please try 2.26? thx |
Is this now a different server?
|
Ok I reverted the parallel execution of the 4 protocols and only enabled the fix with ( ) in the OData. I'M deeply sorry for this ping-pong. |
the dependencies file ist already there right? |
Alternatively can you create a mini deps file with contains only the file system source and a couple of packages from the file share. Is running paket update on this also slow? |
it was the filesystem scanning. After ignoring the filesystem there is no wait and it works |
ok. so we need to investigate this then. |
is this still relevant? |
No I think you can close the issue Den tir. 8. mar. 2016, 16.49 skrev Steffen Forkmann <
|
I tried to convert a project from nuget to paket.
but paket stops, looks like its waiting for something that doesn't happen.
Paket has put a json file in nuget cache folder with the following content
paket.dependencies
packages folder

Check to see if nuget server was not responding, but it was.
Any ideas?
The text was updated successfully, but these errors were encountered: