galleryserver Issue Tracker Rss Feed

Created Issue: Now impossible to clone the repository. [49]

mstpierre — Wed, 23 Jan 2013 23:12:42 GMT

I am not able to clone the repository.
I have tried several times at different periods of the past several days.
I have attempted to clone a (mine) fork (Clone URL: https://hg.codeplex.com/forks/mstpierre/tentative ) with the same result. I do not know if it is the repository that has got corrupted somehow or if the Mercurial service of the CodePlex is deficient in certain cases, one of which Microsoft is remotely connected to.

The fact is that I need access to it.
I would be happy to contribute if it's what it takes to make it work. To make it work because the package currently available in the download needs quite a few tweakings before you can get the read-only operations working. Let alone pushing a package to the server which I am still paddling about.

May I help?

Mat

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

davidebbo — Tue, 12 Jul 2011 23:30:32 GMT

Commented Issue: Gallery Server Gets in Inconsistent state and Fails to Delete package [48]

Haacked — Mon, 11 Jul 2011 22:25:46 GMT

See work item http://nuget.codeplex.com/workitem/1269 for an example.
Somehow, a package record in the gallery server existed, but the corresponding .nupkg file did not.

Repro steps:
1. Push a package to the back-end, but don't let it sync to the front-end.
2. Delete the .nupkg file.
3. Try to delete the package using nuget.exe.

Expected result: Delete the package
Actual result: Exception message.

Ideally we should prevent getting into this state in the first place, but it would be nice if we could recover gracefully.
Comments: Note, the repro steps I provided are not to reproduce the original issue. They are only meant to get the site in the error condition. This bug is to make our site more fault tolerance. We should also try and investigate the steps to get into this condition in the first place.

Created Issue: Gallery Server Gets in Inconsistent state and Fails to Delete package [48]

Haacked — Mon, 11 Jul 2011 22:21:04 GMT

Created Issue: ClickToBuildRelease.bat fails, script is copying Debug files for NuPackPackageFactory. Package pushing fails. [47]

SDeKock — Wed, 22 Jun 2011 22:09:35 GMT

I'm setting up a gallery by following the instructions on nuget.org.
Pushing packages fails because the NuPackPackageFactory plugin is not copied when running the ClickToBuildRelease.bat on a clean checkout.
It's copying the files from bin\Debug\ instead of bin\Release\

These are the incorrect lines:

copy "Plugins\src\NuPackPackageFactory\bin\Debug\NuGet.Core.dll" %destinationDirectory%
copy "Plugins\src\NuPackPackageFactory\bin\Debug\NuPackPackageFactory.dll" %destinationDirectory%

Should be:

copy "Plugins\src\NuPackPackageFactory\bin\Release\NuGet.Core.dll" %destinationDirectory%
copy "Plugins\src\NuPackPackageFactory\bin\Release\NuPackPackageFactory.dll" %destinationDirectory%

This is the exception I get when I publish a package:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Request Error</title>
<style>BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; } #content { margin-left
: 30px; font-size: .70em; padding-bottom: 2em; } A:link { color: #336699; font-weight: bold; text-decoration: underline; } A:visited { color
: #6699cc; font-weight: bold; text-decoration: underline; } A:active { color: #336699; font-weight: bold; text-decoration: underline; } .hea
ding1 { background-color: #003366; border-bottom: #336699 6px solid; color: #ffffff; font-family: Tahoma; font-size: 26px; font-weight: norm
al;margin: 0em 0em 10px -20px; padding-bottom: 8px; padding-left: 30px;padding-top: 16px;} pre { font-size:small; background-color: #e5e5cc;
padding: 5px; font-family: Courier New; margin-top: 0px; border: 1px #f0f0e0 solid; white-space: pre-wrap; white-space: -pre-wrap; word-wra
p: break-word; } table { border-collapse: collapse; border-spacing: 0px; font-family: Verdana;} table th { border-right: 2px white solid; bo
rder-bottom: 2px white solid; font-weight: bold; background-color: #cecf9c;} table td { border-right: 2px white solid; border-bottom: 2px wh
ite solid; background-color: #e5e5cc;}</style>
</head>
<body>
<div id="content">
<p class="heading1">Request Error</p>
<p xmlns="">The server encountered an error processing the request. Please see the <a rel="help-page" href="http://<redacted>/PackageFiles/help">service help page</a> for constructing valid requests to the service. The exception message is 'Could not find a type implementing 'IPackageFactory' in assemblies in the directory 'C:\nugetgallery\Services\GalleryServer\src\Gallery.Server\bin'.'. See server logs for more details. The exception stack trace is: </p>
<p> at Gallery.DependencyResolution.PluginService.FindPluginImplementation[TBase]() in c:\nugetgallery\Services\GalleryServer\src\Gallery.DependencyResolution\PluginService.cs:line 33
at Ninject.Activation.Provider`1.Create(IContext context) in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Provider.cs:line 39
at Ninject.Activation.Context.Resolve() in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Context.cs:line 157
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Ninject.Activation.Providers.StandardProvider.Create(IContext context) in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Providers\StandardProvider.cs:line 81
at Ninject.Activation.Context.Resolve() in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Context.cs:line 157
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Ninject.Activation.Providers.StandardProvider.Create(IContext context) in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Providers\StandardProvider.cs:line 81
at Ninject.Activation.Context.Resolve() in d:\BuildAgent-03\work\b68efe9aafe8875e\src\Ninject\Activation\Context.cs:line 157
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
at Gallery.DependencyResolution.NinjectDependencyResolver.Resolve(Type typeToResolve) in c:\nugetgallery\Services\GalleryServer\src\Gallery.DependencyResolution\NinjectDependencyResolver.cs:line 41
at System.ServiceModel.InstanceContext.GetServiceInstance(Message message)
at System.ServiceModel.Dispatcher.InstanceBehavior.EnsureServiceInstance(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</p>
</div>
</body>
</html>

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

davidebbo — Thu, 02 Jun 2011 17:56:25 GMT

Created Issue: Server should call client for immediate updating [46]

shanselman — Mon, 23 May 2011 22:41:31 GMT

The 1 minute wait while the client catches up to the server is too long. The Server should be able to CALL the client and/or there should be a "force update" from the client. I'm also worried about how the current system will scale with millions of packages.

Created Issue: Create an End Point that both creates & publishes a package [45]

osbornm — Mon, 16 May 2011 22:58:34 GMT

Currently there are two separate end points for creating and publishing a package in the gallery. Given that the 95% case for pushing a package to the gallery is that you want to create it and have it be published, this causes extra client posts. There should be an end point that does both the create and publish of a package to reduce the amount of over head on a client the consumes the Gallery Server (aka NuGet.exe)

Commented Issue: Rating algorithm is too naive [44]

kevink — Tue, 26 Apr 2011 18:20:45 GMT

Right now the value stored in the Rating field of each package in the feed is the average rating. We need to change it to something that takes the number of votes into account and also number of downloads into account.
Comments: Yeah, I don't think we want to change the meaning of Rating. I remember seeing that blog post about building a popularity algorithm before - don't remember if it was Sebastien or Phil, but somebody mentioned it early on in the project as a future consideration. Now that we have ratings in place, it would be a good time to look at implementing that algorithm.

Commented Issue: Rating algorithm is too naive [44]

sebastienros — Tue, 26 Apr 2011 15:46:10 GMT

Right now the value stored in the Rating field of each package in the feed is the average rating. We need to change it to something that takes the number of votes into account and also number of downloads into account.
Comments: Don't call it Rating then, but popularity. http://blog.linkibol.com/2010/05/07/how-to-build-a-popularity-algorithm-you-can-be-proud-of/ Though you still "rate" a package, it's ordered by popularity.

Commented Issue: Rating algorithm is too naive [44]

Haacked — Tue, 26 Apr 2011 15:42:09 GMT

Right now the value stored in the Rating field of each package in the feed is the average rating. We need to change it to something that takes the number of votes into account and also number of downloads into account.
Comments: We should require at least 5 ratings (or some such number) and the secondary sort should be Download count, not alphabetical as it appears to be.

Commented Issue: Rating algorithm is too naive [44]

dfowler — Tue, 26 Apr 2011 07:49:45 GMT

Commented Issue: Rating algorithm is too naive [44]

davidebbo — Tue, 26 Apr 2011 07:34:46 GMT

Right now the value stored in the Rating field of each package in the feed is the average rating. We need to change it to something that takes the number of votes into account and also number of downloads into account.
Comments: Not quite following you. What formula do you suggest to calculate the rating? My take is that the rating value should not take into account those two values, *but* we can treat a package as unrated until it has been voted at least 5 times (or something).

Created Issue: Rating algorithm is too naive [44]

dfowler — Tue, 26 Apr 2011 06:48:01 GMT

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

davidebbo — Wed, 20 Apr 2011 20:48:42 GMT

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

kevink — Wed, 20 Apr 2011 20:11:30 GMT

If you look at the OData feed for RouteMagic 0.1.0, you can see:

<d:GalleryDetailsUrl>http://localhost:777/Packages/Packages/Details/RouteMagic-0-1-0</d:GalleryDetailsUrl>

But in RouteMagic 0.2.2 it becomes:

<d:GalleryDetailsUrl>http://localhost:777/Packages//Details/RouteMagic-0-2-2</d:GalleryDetailsUrl>

Note that the difference is I used the website for the first version, but the NuGet.exe command line for the second one.
Comments: Okay, then that's a problem. I suspect you're right - packages pushed via nuget.exe vs. uploaded through the gallery are probably ending up with a NULL package type. Thinking about it now, I believe I know how this was overlooked. The package type value didn't use to matter on the server side. When a new package syncs over to the Orchard side, we automatically select the package type value if there is only one term defined in the taxonomy, which is the case for NuGet. So on the front-end everything has a value. At some point we added that GalleryDetailsUrl property to the feed - I think it was right before v1 was released. That was the first time that the value mattered for the feed, but we never considered the fact that packages pushed from nuget.exe won't have that value. I think this is something we'll need to add to GalleryServer. In the meantime, I can think of one workaround that should work for NuGet. Since you only have one type you could make 'Package' the default value in the database to handle new submissions, then just update all the existing null values.

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

davidebbo — Wed, 20 Apr 2011 17:39:06 GMT

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

kevink — Wed, 20 Apr 2011 13:01:48 GMT

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

aldion — Tue, 19 Apr 2011 22:11:27 GMT

Commented Issue: GalleryDetailsUrl is incorrect when publishing to feed [42]

davidebbo — Mon, 18 Apr 2011 22:32:22 GMT