Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. rhessinger

    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!

    rhessingerR Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 804
    • Groups 2

    rhessinger

    @rhessinger

    inedo-engineer
    31
    Profile views
    804
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    rhessinger Unfollow Follow
    inedo-engineer administrators

    Best posts made by rhessinger

    • RE: ProGet slow fetching cargo packages

      Hi @jolaka9284_9458,

      Thanks for providing all these details. I was able to pinpoint the reason for the slow down and why it specifically happens on some crates and not others. This is related to some code that we have to determine when to point cargo to pull dependencies from ProGet vs crates.io. Specifically this comes from cargo's API specs for dependencies:

      registry — cargo metadata uses a value of null to indicate that the dependency comes from crates.io. The index uses a value of null to indicate that the dependency comes from the same registry as the index. When creating an index entry, a registry other than crates.io should translate a value of null to be https://github.com/rust-lang/crates.io-index and translate a URL that matches the current index to be null.

      As you can see, the value specified in the metadata is different than the value the index needs to return. In ProGet, we will return null if the package exists in the feed (including connectors) and https://github.com/rust-lang/crates.io-index if it does not. This is to support the case when ProGet is not used as a mirror and instead for only local crates. Unfortunately the use ProGet as a mirror option is stored only in the client config and is not sent to ProGet.

      This is the reason why crates with a lot of dependencies take longer to generate the index than ones that don't and why you'll occasionally get timeouts, but after the retry it works. We have some caching on this to help with performance, but it's not a forever cache.

      I'm going to work on some potential improvements for this and will let you know when I have a solution ready. Unfortunately, the only workaround we have for this currently is to use a package approval workflow (like our npm Package Approval blog article).

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Run proget container as non root

      Hi @kichikawa_2913,

      I have an idea on how to accomplish this. It looks like Docker allows you to expose ports in the run command. Here is what I'm thinking should work. The first thing to do is to map a volume to /usr/share/Inedo/SharedConfig. In my example, I'll map to SharedConfig.

      So here would be the steps to try:

      1. Create the config file using port 8080
      echo '<?xml version="1.0" encoding="utf-8"?><InedoAppConfig><ConnectionString Type="SqlServer">'"`$SQL_CONNECTION_STRING"'</ConnectionString><WebServer Enabled="true" Urls="http://*:8080/"/></InedoAppConfig>' > SharedConfig/ProGet.config
      
      1. run the container using the following command
      podman run -d --userns=keep-id -v proget-packages:/var/proget/packages -v  `SharedConfig:/usr/share/Inedo/SharedConfig` -v /etc/pki/ca-trust/source/anchors:/usr/local/share/ca-certificates:ro --expose=8080 -p 8080:8080 --name=proget -e ASPNETCORE_URLS='http://+:8080' -e SQL_CONNECTION_STRING='Server=SERVERNAME;Database=ProGet;User ID=USERNAME;Password=PASSWORD' -e TZ='America/New_York' -i -t proget.inedo.com/productimages/inedo/proget:5.3.32 /bin/bash
      

      Can you please give that a try?

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: ProGet 5.3.6 SQL Exception

      Hi @gravufo,

      Would you be able to rerun the database scripts on your database? You will just need to run the Run inedosql to update the database step of our manual install guide. Can you see if this fixes your issue?

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Unable to save changes to Role Configuration Script in Otter 2023 and 2023.1 (Build 3)

      Hi @MY_9476,

      Thanks for bringing this to our attention. I added a ticket, OT-502, to fix the issue. This should be released next week in Otter 2023.2.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: BuildMaster 2024.6 - Build .NET Project script template bug

      Hi @mwatt_5816,

      Thanks for all of the detail. I have fixed the code, BM-3982, for this template and it will be released in the next maintenance of BuildMaster 2024.0.7 on Friday.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Error getting npm package versions: The JSON value could not be converted to System.DateTime ...

      Hi @jeff-peirson_4344,

      I have been able to recreate the issue and created a ticket, PG-2870, to track the fix. We expect this to release in ProGet 2024.25 on January 24, 2025. This looks to be related to the package name existing on npmjs.org with all versions being unlisted. If you need a fix sooner, we can provide a pre-release version of ProGet 2024.25 that includes the fix.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: ProGet 6.0.11 (Build 25) allow to use LDAP in Free version

      Hi @NUt ,

      Thank you for bringing this to our attention. This bug, PG-2126, will be fixed in ProGet 6.0.12. Going forward it will allow you to configure everything and even test it via the "Test User Directories" button, but it will only allow you to login using the Built-In user directory and the username/password login option when using ProGet free.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: ProGet 5.3.6 SQL Exception

      Hi @gravufo,

      Great! Glad to hear it! Please post back if you find anything else.

      I also recommend that you switch to the Inedo Hub in the future. We are in the process of deprecating our traditional installer. The Inedo Hub has the ability to update an installation previously installed with the traditional installer and the Inedo Hub now supports offline installations as well, if you need that functionality.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Timeout errors after upgrade to 5.3.7

      Hi @markus4830,

      I'm definitely sorry about this. The change was made to help to aide in improvements to other areas of the system related to NuGet. Unfortunately, it looks like it affected the NuGet API. Expect a more permanent solution in the near future.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Connection issues when configuring LDAP on Linux container

      Hi @kichikawa_2913,

      I think I have identified the issue. I have just pushed another version of InedoCore, version 1.10.7-CI.2 . Could you update and give that a try? I also added an option to bypass the LDAPS certificate verification. It is something that I would only use while testing. The solution you have with adding your certificates as valid certs is a more secure solution. One last thing to make sure you set is the Domain Controller Host. It can just be set to your domain (ex: domain.network using your steps from above). Linux/Docker does not seem to translate domain URLs the same way windows does.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger

    Latest posts made by rhessinger

    • RE: Cannot connect to personal github repo on Buildmaster 26

      Hi @naturescenes13,

      I don't think this is actually an issue with BuildMaster and I instead think this is an issue with GitHub itself. Our GitHub implementation is actually implemented against the github.com API spec and not GitHub enterprise. With that said, the APIs we use actually align between both GitHub products. You can see our implementation here: https://github.com/Inedo/inedox-github/blob/master/GitHub/InedoExtension/Clients/GitHubClient.cs

      With that said, I tried to create a username with an underscore and GitHub completely blocks me from that saying it is an unsupported character. The error message I get is Username may only contain alphanumeric characters or single hyphens, and cannot begin or end with a hyphen. My guess is the some of the API's still accept the old usernames and some of them don't (most likely the newer ones). We probably would need to convert the underscore to some other character (like a - or something) to bypass that. Searching around I see this issue on other open source repositories that wrap GitHub's APIs have the same problem.

      Without being able to recreate the issue first hand, I don't feel comfortable trying to apply a fix without the ability to test the fix. Especially since underscores are not a supported character anymore.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Cannot connect to personal github repo on Buildmaster 26

      Hi @naturescenes13,

      Thanks for the detailed information. Let me run some test's on our side and I will provide an update within the next couple of days.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Cannot connect to personal github repo on Buildmaster 26

      Hi @naturescenes13,

      Can you confirm which version of BuildMaster and the version of GitHub extension you are using? I tested with BuildMaster 2026.4, a classic GitHub PAT, and a personal repository and I'm not seeing any issues.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: Cannot connect to personal github repo on Buildmaster 26

      Hi @naturescenes13,

      What scopes do you have selected for your GitHub personal access token (classic)? Also, do you see any errors in the the diagnostics center? A 404 should only be returned when the namespace does not exist or if the PAT does not have access.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: PGV-2129406 (CVE-2021-26701) flags System.Text.Encodings.Web 4.5.1, 4.7.2, 5.0.1, 8.0.0 and 9.0.0–9.0.21; its version range looks open-ended

      Hi @peter.shrosbree,

      Thank you for your detailed analysis of this issue. We were able to discover a version mismatch error in our NuGet V3 Package Metadata API. Once we retrieved vulnerabilities for a package name, we built the vulnerability array for each version by only checking for a version, not package name. So vulnerabilities that had multiple package names associated could show for multiple packages. This is only an issue with the NuGet API, as internal ProGet mechanisms check differently. Turns out this has been an issue for quite a while now, but it only became noticeable once we launched the NuGet Vulnerability API implementation in 2026.11. We will have this fixed, PG-3410, in tomorrows release of ProGet 2026.13. There is also an issue, PG-3401, that fixes an issue in the NuGet Vulnerability API when a single version is affected.

      As for the security.inedo.com page for PG-2129406, the version range is actually correct. The version range of ≥ 4.0.0 & < 4.5.1 is the same as [4.0.0,4.5.1) which means versions greater than or equal to 4.0.0 and less than 4.5.1. That is why the package in the ProGet UI did not display a vulnerability for 8.0.0 - 9.0.21.

      Please let us know if you need better clarification on any of this.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: How can i exclude npm packages from pgutil

      Hi @Valentijn,

      It looks like when we migrated pgscan in to pgutil, the functionality for this was removed. We will add a new flag to pgutil builds scan called --do-not-scan-npm that will ignore scanning for npm packages. I should have this released later this week or early next week. I will let you know as soon as we push the change.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: PyPI connector to Azure Artifacts returns 401, same URL and PAT work with curl

      Hi @carl.westman_8110,

      Always happy to help! I have actually already made the fix internally. If you would like, I can provide a pre-release build of ProGet 2026.13 that includes the fix.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: PyPI connector to Azure Artifacts returns 401, same URL and PAT work with curl

      Hi @carl.westman_8110,

      I did a little more digging. The actual issue was that the Azure Simple API was including extra information in the response Content Type. That triggered our connector to switch to the old HTML based parsing, which prevented the files from being found. I have corrected this in PG-3399, which is due out October 16, 2026 in ProGet 2026.13.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: ProGet: Delete Asset History Files

      Hi @Ashley,

      I can confirm that F7\._proget_file_history_ is specific to the Feed with an ID 7.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger
    • RE: PyPI connector to Azure Artifacts returns 401, same URL and PAT work with curl

      Hi @carl.westman_8110,

      I ran a test against our test Dev Ops instance. I created a connector and I used basic authentication with my Microsoft account username (my email) as the username and the PAT as the password. I found it was finding my package, but ADO's simple API was not returning the file list which is causing our connector to skip over it. We are currently investigating this further.

      As a work around, have you tried importing those packages into your ProGet feed? You can do that by using Import Package -> Download Package from Another Source. That will allow you to import all the packages and version from your ADO artifact feed.

      Thanks,
      Rich

      posted in Support
      rhessingerR
      rhessinger