I should not this is happening with both restore and update (stuff i tested)

That sounds really strange. The parallel calls are not matching the results? So that's a bug in the async parallel calls?

/cc @dsyme ever heard of something like that in other F# code?

Is there a way to reproduce this behavior? What did you change exactly to make it work?

I used Monitor.Enter Paket.Constants.InUse in the download packages method but this is not ok because it is not intended to be used in async

Could you also please test with version 1.21.1?

Have no idea how to reproduce it, on my machine it works fine but on the new build servers it happens.

Any details about the installed .NET framework versions? And does the
1.21.1 work?
On Aug 7, 2015 11:29 AM, "SavaNDragos" [email protected] wrote:

Have no idea how to reproduce it, on my machine it works fine but on the
new build servers it happens.

—
Reply to this email directly or view it on GitHub
#966 (comment).

Tested it with 1.21.1 and is still happening.
the machine have .net framework 4.5.2 and VS 2013.

Ok good, so at least this is not an error in the latest FSharp.Core.
I'm currently in vacation, but I'd love to investigate this on Monday. I
hope we can find the issue.
On Aug 7, 2015 11:45 AM, "SavaNDragos" [email protected] wrote:

Tested it with 1.21.1 and is still happening.
the machine have .net framework 4.5.2 and VS 2013.

—
Reply to this email directly or view it on GitHub
#966 (comment).

I rerun the same tests i have done on windows 8 and everything works fine. Also the old servers are fine (Windows server 2008 with .net framework 4.5.2 and VS 2010, 2012, 2013).
Conclusion is only affected from what I have seen Windows Server 2012 R2 (maybe the R2 matters).

Ok so played a little bit more: so if we make some async operations to runSynchroniosly paket works fine (just strange, was expected to fail after a couple of tries but it looks fine).
My changes where:
1.In let getFromUrl (auth:Auth option, url : string) ... return client.DownloadString(Uri(url))
2.in let getXmlFromUrl (auth:Auth option, url : string) ... return client.DownloadString(Uri(url))
3.in let safeGetFromUrl (auth:Auth option, url : string) ... let raw = client.DownloadString(Uri(url))
In let getDetailsFromNuGetViaODataFast\let getDetailsFromNuGetViaOData:
4.5.let raw = getFromUrl(auth,url) |> Async.RunSynchronously
6.let raw =
match response with
| Some(r) -> async { return r } |> Async.RunSynchronously
| None ->
let url = sprintf "%s/odata/Packages(Id='%s',Version='%s')" nugetURL package (version.ToString())
getXmlFromUrl(auth,url) |> Async.RunSynchronously

Could you please send a pull request for easier diff?

Btw: thanks for being so patient and helping with finding the root cause.
On Aug 7, 2015 16:18, "SavaNDragos" [email protected] wrote:

Ok so played a little bit more: so if we make some async operations to
runSynchroniosly paket works fine (just strange, was expected to fail after
a couple of tries but it looks fine).
My changes where:
1.In let getFromUrl (auth:Auth option, url : string) ... return
client.DownloadString(Uri(url))
2.in let getXmlFromUrl (auth:Auth option, url : string) ... return
client.DownloadString(Uri(url))
3.in let safeGetFromUrl (auth:Auth option, url : string) ... let raw =
client.DownloadString(Uri(url))
In let getDetailsFromNuGetViaODataFast\let getDetailsFromNuGetViaOData:
4.5.let raw = getFromUrl(auth,url) |> Async.RunSynchronously
6.let raw =
match response with
| Some(r) -> async { return r } |> Async.RunSynchronously
| None ->
let url = sprintf "%s/odata/Packages(Id='%s',Version='%s')" nugetURL
package (version.ToString())
getXmlFromUrl(auth,url) |> Async.RunSynchronously

—
Reply to this email directly or view it on GitHub
#966 (comment).

I have created the pull #969

Have you managed to look over the pull request?

Yes, but I try to reproduce this on our own 2012 R2 servers. No luck. Does
paket's own build work for you?
On Aug 10, 2015 2:31 PM, "SavaNDragos" [email protected] wrote:

Have you managed to look over the pull request?

—
Reply to this email directly or view it on GitHub
#966 (comment).

the build with the modifications i made works perfect
for replication you need the old build (whitout the proposed changes)

yes that's what I meant. if you clone the current Paket repo on your 2012
R2 servers and just run build.cmd - does that repro the failure for you?

2015-08-10 14:48 GMT 02:00 SavaNDragos [email protected]:

the build with the modifications i made works perfect
for replication you need the old build (whitout the proposed changes)

—
Reply to this email directly or view it on GitHub
#966 (comment).

Everything executed ok so all tests pass.

yep same here I tried to run this like 10 times. I can't reproduce your error.
can you create a small project were it reproduces? I really want to fix that guy

/cc @part-timeDev

We are using a lot of internal libraries from our internal feed, tried to replicate with only libraries from nuget.org but couldn't. Also I downgraded a paket to nuget and nuget has no issue with getting the packages.
No idee why the issue happens but I know that is in the async code.

yes I understand that's related to the async code (maybe there is a compiler/jit bug). but I need to debug the real issue. If I just disable the parallel stuff then we have slow restore and don't really know why.

you replaced AsyncDownloadString (from FSharp.Core) with DownloadString. How about trying a task based async version and converting to F#'s async!?

look at #971 I wonder if that would work better.

going to test it in the next 30 min

added also DownloadFileTaskAsync

I tested it several times (the changes you made) and it works. Can you create a new version?

@dsyme @latkin @mexx @tpetricek this suggestes that the bug is somewhere in https://github.com/fsharp/fsharp/blob/0313094fa5d19fd871c83e7e45c35d1fad65daf9/src/fsharp/FSharp.Core/control.fs#L2156

@SavaNDragos yes will do.

@SavaNDragos done.

thanks, I will start now to deploy it on the servers :d

Run it on the build server with a clean cache and error is still there (less packages failling).

This is absurd, the changes you made works but the executable I downloaded seem to have an issue, so i downloaded the code again compiled it obtained the lose files and deployed them and succes. Will wait till tomorrow to see what happens. [one server with run with the downloalded executable also]

"I downloaded seem to have an issue" .. the same issue

Maybe I messed up the release. Will check later
On Aug 10, 2015 7:20 PM, "SavaNDragos" [email protected] wrote:

"I downloaded seem to have an issue" .. the same issue

—
Reply to this email directly or view it on GitHub
#966 (comment).

I think the late part was an issue from my side, I installed latest version with choco and the error persisted so I just downloaded the executable and deployed it manually on a build server.
All builds on that server looks great no paket issue dedected.
I will clear the nuget cache on 2 other build servers and deploy paket 1.26 to confirm that everything is perfect.

so it's fixed in 1.26.0 and we can close this case?

if yes, then please open an issue at https://gitter.im/Microsoft/visualfsharp - it seems we have identified an issue with AsyncDownloadString in FSharp.Core.

@SavaNDragos since you are the only one that can reproduce that error, are you up for further rounds of testing? If the issue is really outside of Paket (whereever that might be) then we still want to fix that.

sounds good, I have allready cloned a build server

I think it should be marked as resolved