-
Notifications
You must be signed in to change notification settings - Fork 70
Add missing source files referenced by PDB. #19
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
Conversation
…ger than 21,474,836 bytes (int.Max/100) that was generating negative download percentage completion
|
Hi @tom-englert, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution! TTYL, DNFBOT; |
|
@tom-englert, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR. |
|
Sweet, thanks for sticking through this long process! We will take a look CC @tmat |
|
@tom-englert Can you please add a test case ? |
|
@yishaigalatzer this is just wrapping existing stuff that is already unit tested (it does not make sense unit-testing DisSymReader here). I'm not the friend of adding dummy unit tests just for the sake of having a unit test. |
|
Completely agree. Command line tests in nuget.client repo are where the integration tests live. Yishai From: Tom Englertmailto:notifications@github.com @yishaigalatzerhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fyishaigalatzer&data=01%7c01%7cyigalatz%40microsoft.com%7c092e355146064ee4e6c408d2d6cae03c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=yq2umMiCT0X3XoBpH%2ft9H%2fKKMxjZNDrqB8DdLteJHjY%3d this is just wrapping existing stuff that is already unit tested (it does not make sense unit-testing DisSymReader here). I'm not the friend of adding dummy unit tests just for the sake of having a unit test. — |
attempt to purge temp cache completely when no cached expanded folder…
|
@tmat - When do you plan to turn the RC into RTM? |
|
Within a week or so. |
|
replaced with #23 based on 2.10 branch |
Fix for NuGet/Home#304