Skip to content
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

NuGet packaging hangs if content folder contains too many files #348

Closed
neurospeech opened this issue Apr 2, 2015 · 7 comments
Closed
Assignees
Labels
Functionality:Pack Priority:2 Issues for the current backlog. Type:Bug
Milestone

Comments

@neurospeech
Copy link

Checked and verified, till 55 content files NuGet had no problem, but when we reached 65 content files, NuGet hangs and does not create new package.

@ChrisSfanos
Copy link

Can you please provide specific repro steps, specifically the command you ran and the types/sizes of the files you are using to generate the package

@ChrisSfanos ChrisSfanos added this to the 3.1.0-Beta milestone Apr 7, 2015
@ChrisSfanos
Copy link

If you've uploaded the package to NuGet, please send us the link

@neurospeech
Copy link
Author

I have this repository, https://github.com/neurospeech/atoms.js which contains "nuget/Atoms.js" folder. And you can see nuget specs.

https://github.com/neurospeech/atoms.js/blob/master/nuget/Atoms.js/Package.nuspec

Inside "style" folder of my repository root, I have style sheets that are included in nuget package. But it looks like, if I add more LESS files, NuGet packager halts completely if there are more than current number of files.

https://github.com/neurospeech/atoms.js/tree/master/style

I had added 5 more LESS files, and I noticed the problem. Eventually, we combined all LESS files into one Unsorted.less file, that reduced total number of files, and we were able to build package.

@thomerow
Copy link

Has there been any progress on this? Today I ran into the same problem. If the number of files is greater than a certain number (49 in my case – the file sizes don't seem to matter), nuget.exe pack never exits.

@yishaigalatzer
Copy link

We haven't made much progress on this unfortunately. We plan to refactor pack to stop using OPC, and hopefully that should also resolve this issue.

@yishaigalatzer yishaigalatzer modified the milestones: 3.4, 3.3.0 Nov 25, 2015
@yishaigalatzer yishaigalatzer added Priority:2 Issues for the current backlog. Type:Bug labels Nov 25, 2015
@yishaigalatzer yishaigalatzer modified the milestones: 3.4 Beta, 3.4 RTM Feb 25, 2016
@yishaigalatzer yishaigalatzer modified the milestones: 3.4 RTM, 3.4 RTM - Triage Mar 11, 2016
@emgarten
Copy link
Member

@toddm would you check if this repros in 3.5.0?

@toddm
Copy link

toddm commented Mar 25, 2016

I cloned the repo, added 10 more css files, and did a pack with 3.5.0 and it worked without any problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Functionality:Pack Priority:2 Issues for the current backlog. Type:Bug
Projects
None yet
Development

No branches or pull requests

5 participants