lprun hitting concurrency issues when compiling scripts in parallel

I have a LinqPad script which uses Util.CompileAsync in parallel to compile and run several other .linq files. When this happens on a machine without the LinqPad NuGet cache populated (at %LOCALAPPDATA%\LINQPad\NuGet.FW46) I sometimes see one or more compilations fail because of multiple threads trying to access the LINQPadPackageInfo.xml file stored within each package.

Is this a known bug? Is there a workaround?

Comments

  • Yes, this is probably an oversight. I'll look into adding a mutex to the next build.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!