Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. pmsensi
    P
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Pedro

    @pmsensi

    0
    Reputation
    17
    Posts
    1
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online
    Website sensirion.com/ Location Zurich, Switzerland

    pmsensi Follow

    Best posts made by pmsensi

    This user hasn't posted anything yet.

    Latest posts made by pmsensi

    • RE: Error 500 when trying to restore NuGet packages

      Hi @atripp ,

      thank you for the update. I reverted to 2025.07 and I will wait for the next maintenance release.

      @power_pille thank you too, for your findings and suggestions.

      posted in Support
      P
      pmsensi
    • RE: Error 500 when trying to restore NuGet packages

      I'm having the same problem, and I can see in the database the duplicated entries.

      8f70a461-236b-4ea3-b01e-118e940a726c-image.png

      posted in Support
      P
      pmsensi
    • Get Package Policies using ProGetClient

      Hello,

      Is it possible to get the Package Policies with ProGetClient? I'm interested in the License Rules.

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • Get package license with ProGetClient

      Hello,

      I was trying to use ProGetClient to get the license information from a NuGet package present on a feed, but I didn't find any method to get that information.

      I know I can use the NuGet CLI to get that information, but if the license is set on ProGet GUI, the returned license is not what we have on ProGet, but what is present in the package metadata.

      As an example, the System.Memory 4.5.5 has a URL license, and on ProGet, it was set to MIT.

      27cd1701-e1c5-48d8-a2a4-8302d307be07-image.png

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • RE: Publish a Docker image from Gitlab pipeline using Kaniko to Proget

      Hello @atripp ,

      Thank you for your help.

      We have an intermediate certificate (proxy), which I think, as you point out, can be the problem. I will clarify with our IT department. Anyway, after reading a little bit more, there is a variable to force Kaniko to use HTTP/1.1.

       variables:
          GODEBUG: "http2client=0"
      

      After adding that, everything works :)

      Thank you!

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • Publish a Docker image from Gitlab pipeline using Kaniko to Proget

      Hello,

      I'm trying to publish a Docker image from Gitlab pipeline using Kaniko to Proget.

      With HTTP, everything goes smoothly, but with HTTPS, an error occurs: stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peer

      I checked all certificates, and they are valid.

      Do you have any advice on continuing the troubleshooting?

      The full error:
      Pushing image to xxx.lokal:8625/dev-images/image-name:latest
      error pushing image: failed to push to destination xxx.lokal:8625/dev-images/image-name:latest: Head "https://xxx.lokal:8625/v2/dev-images/image-name/blobs/sha256:944cb9daf72b35ac4c2a49b5ad6d66fd45e201e5fd2a67b47cb5d4b4c838f19e": stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peer

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • RE: SQL error while reading/re-indexing the Directory Assets

      @rhessinger

      I added the requested info to the opened ticket.

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • SQL error while reading/re-indexing the Directory Assets

      Hello,

      while trying to access the asset or re-index, we receive the following error:

      INFO : 2025-02-25 16:13:57Z - Performing verification for Asset feed 3: ToolChainAssets
      INFO : 2025-02-25 16:13:57Z - Deactivating feed.
      INFO : 2025-02-25 16:13:57Z - Re-activating feed.
      ERROR: 2025-02-25 16:13:57Z - Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): FOR XML konnte die Daten für den CreatedBy_User_Name-Knoten nicht serialisieren, weil ein in XML unzulässiges Zeichen (0x0000) enthalten ist. Um diese Daten mithilfe von FOR XML abzurufen, konvertieren Sie sie in den Datentyp "binary", "varbinary" oder "image", und verwenden Sie die BINARY BASE64-Direktive.
         at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
         at Microsoft.Data.SqlClient.SqlInternalConnection.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.TryConsumeMetaData()
         at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData()
         at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
         at Microsoft.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader(Boolean isInternal, Boolean forDescribeParameterEncryption)
         at Microsoft.Data.SqlClient.SqlCommand.EndExecuteReaderInternal(IAsyncResult asyncResult)
         at Microsoft.Data.SqlClient.SqlCommand.EndExecuteReaderAsync(IAsyncResult asyncResult)
         at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
      --- End of stack trace from previous location ---
         at Inedo.Data.SqlServerDatabaseContext.SqlServerCommand.ExecuteReaderAsync(CancellationToken cancellationToken)
         at Inedo.Data.DatabaseContext.DbResult.CreateAsync(IGenericDbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
         at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters, DatabaseCommandReturnType returnType)
         at Inedo.Data.SqlServerDatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters, DatabaseCommandReturnType returnType)
         at Inedo.Data.DatabaseContext.ExecuteNonQueryAsync(String storedProcName, GenericDbParameter[] parameters)
         at Inedo.Data.DatabaseContext.ExecuteScalarAsync[TResult](String storedProcName, GenericDbParameter[] parameters, Int32 outParameterIndex)
         at Inedo.ProGet.Feeds.Assets.AssetFeed.EnsureDirectoryAsync(String fullPath, Nullable`1 created, Nullable`1 modified, IEnumerable`1 userMetadata)
         at Inedo.ProGet.Feeds.Assets.AssetFeed.EnsureDirectoryAsync(String fullPath, Nullable`1 created, Nullable`1 modified, IEnumerable`1 userMetadata)
         at Inedo.ProGet.Feeds.Assets.AssetFeed.<>c__DisplayClass53_0.<<VerifyFeedAsync>g__checkDirAsync|1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Inedo.ProGet.Feeds.Assets.AssetFeed.<>c__DisplayClass53_0.<<VerifyFeedAsync>g__checkDirAsync|1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Inedo.ProGet.Feeds.Assets.AssetFeed.<>c__DisplayClass53_0.<<VerifyFeedAsync>g__checkDirAsync|1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Inedo.ProGet.Feeds.Assets.AssetFeed.VerifyFeedAsync(IFeedVerificationContext context, CancellationToken cancellationToken)
         at Inedo.ProGet.Executions.VerifyFeedExecution.ExecuteAsync(IManualExecutionContext context)
         at Inedo.ProGet.Executions.VerifyFeedExecution.ExecuteAsync(IManualExecutionContext context)
         at Inedo.ProGet.Service.Executions.ActiveManualExecution.ExecuteAsync()
      ClientConnectionId:1cd23f85-8aa0-4309-b006-edd39297c935
      Error Number:6841,State:1,Class:16
      

      This seems to happen after the update to version 24.0.24, but unfortunately, I'm not 100% sure because we don't use this very often.

      We are currently running version 24.0.27 and the problem is still there.

      Best Regards,
      Pedro

      posted in Support
      P
      pmsensi
    • RE: Different query results nuget feed

      Hello @NanciCalo ,

      thank you for the clarification.

      So, as I wrote, the only way to have the expected behavior is to disable the cache from the feed/connector right ? Then the search mechanism will not search for local packages.

      Best Regards

      posted in Support
      P
      pmsensi
    • RE: Different query results nuget feed

      Hi @dean-houston ,

      thank you for your quick response.

      The missing values from the search API are not new, the owners exist since v2 at least.
      I searched for a package that I don't have any local package, then the search works as expected (all versions and owners are there). Then I deleted the cached package (microsoft.playwright.nunit) and the search result contains now all versions and owners.

      So, I would say that for me is a clear relation between the cache and the missing information.

      I understand that can be hard, and can cause performance problems, but the version information is present when I access the package page from ProGet, so, that information should be available over search API and not only the local packages, in my opinion.

      Of course, a possible solution is to disable the cache from that feed/connector. So then, no local packages will be present. Of course, with this change, I will not be able to use the full power/features of ProGet :\

      eccf4489-811b-49da-a1b6-df560e24dc95-image.png
      fac03dfc-297b-4c83-bf82-65b45ac8c21d-image.png

      Regarding the registration API, the amount of data present is huge! A lot of not necessary information and the owners entry is not there too :)

      I would like to point out that, the owners were just an example of the missing properties, there are more missing. But the important ones for me are the versions.

      I'm using the search API in our internal tool to verify if a new version is available, if exists on the feed, etc.
      I encounter this problem, when I was setting our internal tool to only use ProGet feeds (mixed connectors), so that way, we can block internet access (nuget.org) to the server where that tool is running, and only ProGet server will have access to nuget.org.

      Do you see any other way to get all the versions ?

      Thank you for your help.

      posted in Support
      P
      pmsensi