Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. Valentijn
    3. Posts

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ValentijnV Offline
    • Profile
    • Following 0
    • Followers 1
    • Topics 28
    • Posts 76
    • Groups 0

    Posts

    Recent Best Controversial
    • Errors in PackageAnalyzer logs

      Hi,

      I see errors in PackageAnalyzer logs

      Unhandled exception analyzing packages in Vicrea feed: Object reference not set to an instance of an object.
      Unhandled exception analyzing packages in VicreaMaven feed: Object reference not set to an instance of an object.
      Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
         at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__209_0(Task`1 result)
         at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
         at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      --- End of stack trace from previous location ---
         at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
      --- End of stack trace from previous location ---
         at Inedo.Data.DatabaseContext.DbResult.CreateAsync(DbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
         at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
         at Inedo.Data.SqlServerDatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
         at Inedo.ProGet.Data.DB.Context.Projects_GetReleaseAnalyzerDataAsync(Nullable`1 ProjectRelease_Id)
         at Inedo.ProGet.Projects.ProjectReleaseAnalyzer.AnalyzeReleaseAsync(Int32 projectReleaseId, Boolean sendEmail, CancellationToken cancellationToken)
         at Inedo.ProGet.ScheduledTasks.General.PackageAnalyzerScheduledTask.AnalyzeReleasesAsync(ScheduledTaskContext context)
         at Inedo.ProGet.ScheduledTasks.General.PackageAnalyzerScheduledTask.ExecuteAsync(ScheduledTaskContext context)
         at Inedo.ProGet.Service.Executions.ActiveScheduledTaskExecution.ExecuteAsync()
      ClientConnectionId:0d07b9a9-043b-4747-81e1-0bdfc00192d0
      Error Number:-2,State:0,Class:11
      

      After the last error the analysis stops.

      Using Version 2023.32 (Build 3)

      posted in Support
      ValentijnV
      Valentijn
    • Small spelling error in image Usage Instructions

      Hi,

      There is an i in 'the' that shouldn't be there.

      To publish a container image to this registry, you must first retag it with thie repository url, and then push it as follows:

      posted in Support
      ValentijnV
      Valentijn
    • RE: Unable to add license to package

      I upgraded to 23.0.32 (was on 23.0.31) and the license looks ok now but when I run analyze I get a timeout.

      An error occurred in the web application: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

      After that I ran the PackageAnalyzer task but that failed too.

      Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
         at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__209_0(Task`1 result)
         at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
         at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      --- End of stack trace from previous location ---
         at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
      --- End of stack trace from previous location ---
         at Inedo.Data.DatabaseContext.DbResult.CreateAsync(DbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
         at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
         at Inedo.Data.SqlServerDatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
         at Inedo.ProGet.Data.DB.Context.Projects_GetReleaseAnalyzerDataAsync(Nullable`1 ProjectRelease_Id)
         at Inedo.ProGet.Projects.ProjectReleaseAnalyzer.AnalyzeReleaseAsync(Int32 projectReleaseId, Boolean sendEmail, CancellationToken cancellationToken)
         at Inedo.ProGet.ScheduledTasks.General.PackageAnalyzerScheduledTask.AnalyzeReleasesAsync(ScheduledTaskContext context)
         at Inedo.ProGet.ScheduledTasks.General.PackageAnalyzerScheduledTask.ExecuteAsync(ScheduledTaskContext context)
         at Inedo.ProGet.Service.Executions.ActiveScheduledTaskExecution.ExecuteAsync()
      ClientConnectionId:e6772410-67c5-4929-a7c3-c2ad388f8e73
      Error Number:-2,State:0,Class:11
      
      posted in Support
      ValentijnV
      Valentijn
    • RE: Timeout in build when running pgscan

      Hi,

      I checked again and the number of packages is correct when the build succeeds.
      Had to run the build 9 times before I had a build that did not give a timeout.

      Before i counted the number of components in the SBOM but the app itself is also a component and i have two SBOM's so therefore i was missing two packages.

      I get the feeling that during the failing builds the SBOM is uploaded but not completely processed. So the next build its processed and thats when i see three SBOM's or four if the build succeeds.

      Still no clue why this is the only build that has these failures, its not our biggest or most complex product. We don't have many builds that contain both npm and nuget packages but there are others. All builds are run at least once a week so the others with two pgscans are ok.

      posted in Support
      ValentijnV
      Valentijn
    • Unable to add license to package

      Hi,

      I have an issue that says Unknown License Detected for package
      Microsoft.AspNet.Web.Optimization 1.1.3

      But when I use "Assign License Type to URL" and choose an existing license
      (in this case MICROSOFT .NET LIBRARY) and press Add to license nothing seem to happen and the package still has an unknown license.

      I tried to add the package to the license as Package name but its says its invalid
      "pkg:/nuget/Microsoft.AspNet.Web.Optimization" is an invalid package name.

      the same if i try to add it as an PUrl (pkg:/nuget/Microsoft.AspNet.Web.Optimization@1.1.3)

      posted in Support
      ValentijnV
      Valentijn
    • RE: Timeout in build when running pgscan

      I noticed that the new version had multiple SBOM's and I only ran the build once.
      After deleting all SBOM's and the version again the build still failed but at least I only see 1 SBOM this time.

      Edit: The build runs pgscan twice once for npm and once for NuGet so i should see two SBOM's
      499 components in npm SBOM
      137 components in NuGet SBOM
      636 is the expected number of packages

      But this time total packages in UI shows 634

      posted in Support
      ValentijnV
      Valentijn
    • RE: Timeout in build when running pgscan

      Running again into this issue:
      Unhandled exception processing https://packages.vicrea.nl/api/sca/import

      Version 2023.31 (Build 5)
      Total Packages 635

      I deleted the release in Proget and build again, again a timeout but I do see the new release in Proget. So it looks like the SBOM is processed but maybe not complete?

      posted in Support
      ValentijnV
      Valentijn
    • RE: Timeout in build when running pgscan

      I ended up restarting the build 5 times when it finally worked.
      Proget is running on a dedicated machine that does nothing else and no other builds where running.

      Can it be that we have too many SBOMs, versions, packages or something like that?

      posted in Support
      ValentijnV
      Valentijn
    • Timeout in build when running pgscan

      After upgrading to the latest version this started to happen.

      Version: Version 2023.30 (Build 16)

      Server responded with 500 Internal Server Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

      In Diagnostic Center the following is shown:

      Unhandled exception processing https://packages.vicrea.nl/api/sca/import

      Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
      ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
      at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__209_0(Task`1 result)
      at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
      at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      --- End of stack trace from previous location ---
      at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
      --- End of stack trace from previous location ---
      at Inedo.Data.DatabaseContext.DbResult.CreateAsync(DbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
      at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
      at Inedo.Data.SqlServerDatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
      at Inedo.ProGet.Data.DB.Context.Projects_GetReleaseAnalyzerDataAsync(Nullable`1 ProjectRelease_Id)
      at Inedo.ProGet.Projects.ProjectReleaseAnalyzer.AnalyzeReleaseAsync(Int32 projectReleaseId, Boolean sendEmail, CancellationToken cancellationToken)
      at Inedo.ProGet.Projects.BomUtil.ImportXmlAsync(Stream source)
      at Inedo.ProGet.WebApplication.SimpleHandlers.Api.Bom.ScaApiHandler.ProcessRequestAsync(AhHttpContext context, LoggedResponseStream output, WebApiContext apiContext)
      at Inedo.ProGet.WebApplication.SimpleHandlers.Api.ProGetApiKeySecuredHandler.ProcessRequestInternalAsync(AhHttpContext context, LoggedResponseStream output, WrappedApiKey apiKey)
      at Inedo.Web.Handlers.Api.ApiKeySecuredHandler.ProcessRequestInternalAsync(AhHttpContext context)
      at Inedo.Web.Handlers.Api.StandardApiHandler.ProcessRequestAsync(AhHttpContext context)
      ClientConnectionId:6200fa0a-d298-4898-be14-9721cbe745c5
      Error Number:-2,State:0,Class:11
      
      posted in Support
      ValentijnV
      Valentijn
    • RE: Database Error

      Hi,

      I got the same error, after disabling the preview feature it works again.

      An error occurred processing a GET request to https://packages.vicrea.nl/nuget/VicreaNuGet/v3/flatcontainer/system.management.automation.dll/10.0.10586/system.management.automation.dll.10.0.10586.nupkg: 547`16`0`FeedPackageVersions_SetAnalysis`26`The INSERT statement conflicted with the FOREIGN KEY constraint "FK__FeedPackageAnalyses__FeedPackageVersions". The conflict occurred in database "ProGet", table "dbo.FeedPackageVersions".
      
      posted in Support
      ValentijnV
      Valentijn
    • License not found in package

      Hi,

      I'm trying to assign licenses to npm packages that have embedded license files.

      But the kendo packages give an error:
      (500) Server Error License not found in package

      There is a license file in the package but it's called license.md
      https://www.npmjs.com/package/@progress/kendo-licensing

      Regards,

      Valentijn

      posted in Support
      ValentijnV
      Valentijn
    • RE: Enable Vulnerability Feature Preview... timeout

      I tried it four times but all attempts failed.

      posted in Support
      ValentijnV
      Valentijn
    • Enable Vulnerability Feature Preview... timeout

      Hi,

      I tried to enable this feature but got a timeout.
      Running: Version 2023.29 (Build 17)

      Updating internal database with 43011 entries
      Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
      ---> System.ComponentModel.Win32Exception (258): The wait operation timed out.
      at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__209_0(Task1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke()
      at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
      --- End of stack trace from previous location ---
      at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
      --- End of stack trace from previous location ---
      at Inedo.Data.DatabaseContext.DbResult.CreateAsync(DbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
      at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
      at Inedo.Data.SqlServerDatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters)
      at Inedo.Data.DatabaseContext.ExecuteTableAsync[TRow](String storedProcName, GenericDbParameter[] parameters)
      at Inedo.ProGet.Vulnerabilities.PgvdDownloafer.UpdateVulnerabilitiesInternalAsync(IAsyncEnumerable`1 vulnerabilities, CancellationToken cancellationToken)
      at Inedo.ProGet.Vulnerabilities.PgvdDownloafer.UpdateVulnerabilitiesAsync(CancellationToken cancellationToken)
      at Inedo.ProGet.Executions.SwitchToPgvdExecution.ExecuteAsync(IManualExecutionContext context)
      at Inedo.ProGet.Service.Executions.ActiveManualExecution.ExecuteAsync()
      ClientConnectionId:12b1995d-0cc6-4709-9072-3b870d34f096
      Error Number:-2,State:0,Class:11

      posted in Support
      ValentijnV
      Valentijn
    • RE: KeyNotFoundException when using pgscan

      @dean-houston

      This was a package that came from a local workspace, skipping seems the right solution as you can never check these packages for vulnerabilities.

      posted in Support
      ValentijnV
      Valentijn
    • KeyNotFoundException when using pgscan

      Hi,

      We started using Proget and pgscan for our frontend code but get a KeyNotFoundException exception in pgscan\Inedo.DependencyScan\NpmDependencyScanner.cs line 81

      string version = npmDependencyPackage.Value.GetProperty("version").GetString();
      

      This is the bit of json from the lock-file it fails on and as you can see there is no version attribute.

      "node_modules/@vicrea-neuron/eslint-plugin": {
        "resolved": "packages/eslint-plugin",
        "link": true
      },
      

      With kind regards,

      Valentijn

      posted in Support
      ValentijnV
      Valentijn
    • RE: Out of memory errors after upgrading to 2023.15

      Thanks, I updated and feed cleanup is back to seconds instead of hours

      5b6aebe8-48a0-410b-bc47-c5d54f86e8f6-image.png

      posted in Support
      ValentijnV
      Valentijn
    • RE: Out of memory errors after upgrading to 2023.15

      In todays log there is some more information:

      Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): There is insufficient system memory in resource pool 'internal' to run this query.
         at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
         at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
         at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
         at Microsoft.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows)
         at Microsoft.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
         at Microsoft.Data.SqlClient.SqlDataReader.Read()
         at Inedo.Data.StrongDataReader.<Read>g__read|11_1[TRow](<>c__DisplayClass11_0`1& )
         at Inedo.Data.StrongDataReader.Read[TRow](IDbDataResult dbResult)+MoveNext()
         at Inedo.Data.StrongDataReader.Read[TRow](Func`1 getReader, Boolean disposeReader)+MoveNext()
         at Inedo.ProGet.Feeds.StandardPackageFeed`3.<>c__DisplayClass58_0.<<Inedo-ProGet-Feeds-IRetentionFeed<Inedo-ProGet-Feeds-StandardRetentionPackage<TVersion>>-EnumerateItemsAsync>g__iterateOneToOne|1>d.MoveNext()
         at Inedo.EnumerableExtensions.AsyncIterator`1.Enumerator.MoveNextAsync()
         at Inedo.ProGet.Feeds.IRetentionFeed`1.Inedo.ProGet.Feeds.IRetentionFeed.EnumerateItemsAsync(Boolean cachedOnly, Boolean prereleaseOnly, CancellationToken cancellationToken)+MoveNext()
         at Inedo.ProGet.Feeds.IRetentionFeed`1.Inedo.ProGet.Feeds.IRetentionFeed.EnumerateItemsAsync(Boolean cachedOnly, Boolean prereleaseOnly, CancellationToken cancellationToken)+MoveNext()
         at Inedo.ProGet.Feeds.IRetentionFeed`1.Inedo.ProGet.Feeds.IRetentionFeed.EnumerateItemsAsync(Boolean cachedOnly, Boolean prereleaseOnly, CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
         at Inedo.ProGet.Feeds.RetentionRunner.RunRetentionRuleAsync(FeedRetentionRuleConfiguration rule, Int32 sequenceNumber, Boolean retentionDryRun, CancellationToken cancellationToken)
         at Inedo.ProGet.Feeds.RetentionRunner.RunRetentionRuleAsync(FeedRetentionRuleConfiguration rule, Int32 sequenceNumber, Boolean retentionDryRun, CancellationToken cancellationToken)
         at Inedo.ProGet.Feeds.RetentionRunner.PerformRetentionAsync(Boolean dryRun, CancellationToken cancellationToken)
         at Inedo.ProGet.ScheduledTasks.Feed.FeedCleanupScheduledTask.ExecuteAsync(ScheduledTaskContext context)
         at Inedo.ProGet.Service.Executions.ActiveScheduledTaskExecution.ExecuteAsync()
      ClientConnectionId:9f725e0d-f135-46ae-8b92-fb58605389c0
      Error Number:701,State:123,Class:17
      
      posted in Support
      ValentijnV
      Valentijn
    • RE: Out of memory errors after upgrading to 2023.15

      Hi

      I upgrade whenever the website gives me a warning so the previous version was probably 2023.14 (can't find the previous version in the logfile)

      It looks like the problem is with the feed cleanup as that takes a long time and gives an error.

      Vicrea FeedCleanup 8/24/2023 1:43 AM - Normal Executing
      Vicrea FeedCleanup 8/23/2023 1:58 AM 6h 32min Error Completed
      Vicrea FeedCleanup 8/22/2023 1:49 AM 7h 29min Error Completed

      The log doesn't say anything usefull:

      DEBUG: 2023-08-22 23:58:38Z - Beginning cleanup for Vicrea (NuGet) feed.
      INFO : 2023-08-22 23:58:38Z - Starting feed retention check...
      DEBUG: 2023-08-22 23:58:38Z - Checking for feed retention rules...
      DEBUG: 2023-08-22 23:58:38Z - Feed has 1 retention rule.
      INFO : 2023-08-22 23:58:38Z - Running in dry run mode...
      INFO : 2023-08-22 23:58:38Z - Checking rule 1...
      DEBUG: 2023-08-22 23:58:38Z - Only delete packages that have not been requested in the last 90 days (since 5/25/2023 1:58:38 AM)
      DEBUG: 2023-08-22 23:58:38Z - Only delete packages that have been downloaded fewer than 1 times.
      DEBUG: 2023-08-22 23:58:38Z - Never delete the most recent 1 versions of packages.
      INFO : 2023-08-22 23:58:38Z - Finding packages that match retention rule 1...

      posted in Support
      ValentijnV
      Valentijn
    • Out of memory errors after upgrading to 2023.15

      Hi,

      We upgraded to Proget 2023.15 but now every morning the server is unavailable.

      We see low virtual memory warnings in the eventlog mentioning the ProGet service.

      ProGet.Service.exe (2812) consumed 10.343.374.848 bytes,

      posted in Support
      ValentijnV
      Valentijn
    • RE: FeedCleanup deleted way more than expected

      I uploaded the missing packages again by dropping everything I had in my local cache to the DropFolder en got my builds working again.

      But when I look at one of the missing packages its shows up with all the download history when seen from the package itself but when I look at usage from the specific version its shows no recent downloads but only downloads fromn last month.

      From build logs
      NU1101: Unable to find package Neuron.Tenant.Monitor. No packages exist with this id in source(s): Vicrea, VicreaNuGet

      Seen from package
      ac0fcadb-cf11-4f1b-bb9a-033b33ebfcd8-image.png

      Seen from specific version
      d200f9c9-d174-45a8-8709-dc6d5f392c47-image.png

      posted in Support
      ValentijnV
      Valentijn
    • 1 / 1