Posts made by dm.sidelnikov_5266

Hello,
Sometimes (often actually) in "Diagnostic Center" -> "Log Messages" tab I see the following errors:

Message:
An error occurred in the web application: Response Content-Length mismatch: too few bytes written (0 of 23315).
 Details: URL: http://my-proget-url/nuget/sc/v3/flatcontainer/microsoft.net.sdk.maccatalyst.manifest-6.0.100/15.0.101-preview.11.551/microsoft.net.sdk.maccatalyst.manifest-6.0.100.15.0.101-preview.11.551.nupkg
Referrer: (not set)
User: (unknown)
User Agent: NuGet Client V3/6.0.0
Details:
Stack trace: at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ThrowException(Exception exception)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.CompleteAsync(Exception exception)
at System.Web.HttpResponse.CompleteAsync()
at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)

Can you help me to understand is it something significant or I can ignore those kind of errors?

@rhessinger It seems like problem solved inproget:6.0.11. Thanks!

Hello, emailed JSON that you requested to support@inedo.com

Hi, thanks for your reply.
It's hard to share access to Azure DevOps because it is internal, also cant use fiddler in my infrastructure (Proget is hosted in k8s cluster).
May be IIS logs from Azure DevOps will help?

GET /_packaging/58ea41c1-4778-4baa-8554-773dbfb2ef11/nuget/v3/registrations2-semver2/packagename_1/index.json - 443 ProGet/6.0.9.6+(Unix+5.4.0.58) - 404 0 0 25

GET /_packaging/58ea41c1-4778-4baa-8554-773dbfb2ef11/nuget/v3/registrations2-semver2/packagename_1/index.json - 443 ProGet/6.0.9.6+(Unix+5.4.0.58) - 404 0 0 19

GET /_packaging/58ea41c1-4778-4baa-8554-773dbfb2ef11/nuget/v3/flat2/packagename_1/1.0.0/packagename_1.1.0.0.nuspec - 443 ProGet/6.0.9.6+(Unix+5.4.0.58) - 404 0 0 18

GET /_packaging/58ea41c1-4778-4baa-8554-773dbfb2ef11/nuget/v3/registrations2-semver2/5.138.1-pullrequest2740-0012/index.json - 443 ProGet/6.0.9.6+(Unix+5.4.0.58) - 404 0 0 20

Also I need to mention that we using Azure Devops on-premise and its Api can be slight different from online Azure.

I did a test with free Azure DevOps in cloud, connect it to our Proget instance and it is working good without errors that I see with on-premise.

Hello, I setup Proget from docker image, at first it was 6.0.5 version, then I tried latest (6.0.9) version.
I'm struggling with following scenario:
I made a nuget feed and connected it with nuget.org and also connected it with our internal Azure DevOps artifacts feed.
I can see packages from Azure DevOps in Proget search (in feed), but get an error when try to open it:

Message: An error occurred in the web application: Object reference not set to an instance of an object.
Details: URL: http://our_url/feeds/sc/package_name/versions
Referrer: https://our_url/feeds/sc?Search=package_name
User: (unknown)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36
Stack trace: at Inedo.ProGet.WebApplication.Pages.Packages.Versions.ListPackageVersionsPageBase.CreateChildControlsAsync() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp_E194970\Src\ProGet.WebApplication\Pages\Packages\Versions\ListPackageVersionsPageBase.cs:line 88
at Inedo.ProGet.WebApplication.Pages.ProGetSimplePageBase.InitializeAsync() in C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\192.168.44.60\Temp_E194970\Src\ProGet.WebApplication\Pages\ProGetSimplePageBase.cs:line 72
at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync()
at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync(HttpContext context)
at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)

Currently using Proget 6.0.9 Free License