Support

• V

  NuGet no longer works after upgrading to 2024
  22 Apr 2024, 06:04 • v.makkenze_6348   30 Apr 2024, 14:32

  19
  0
  Votes
  19
  Posts
  70
  Views

  J 30 Apr 2024, 14:32

  @stevedennis Thanks for the updated version - it works smoothly now.
• S

  Conda Feed to SMB Share
  24 Apr 2024, 05:37 • scott.wright_8356   29 Apr 2024, 22:26

  8
  0
  Votes
  8
  Posts
  15
  Views

  S 29 Apr 2024, 22:26

  @rhessinger Wonderful, thank you very much and credit to Pawel Ostrowski who also did a lot of investigation on this
• C

  Updating to Proget to 24.0.0 from 23.0.18 gives "Cannot drop the view 'database_firewall_rules', because it does not exist or you do not have permission."
  23 Apr 2024, 12:37 • carl.westman_8110   29 Apr 2024, 06:07

  8
  0
  Votes
  8
  Posts
  25
  Views

  C 29 Apr 2024, 06:07

  @atripp, I can confirm that 2024.1 works great
• D

  NPM Vulnerability with Exception
  26 Apr 2024, 14:19 • dan.brown_0128   26 Apr 2024, 18:40

  4
  0
  Votes
  4
  Posts
  14
  Views

  26 Apr 2024, 18:40

  @dan-brown_0128 I understand So you'd either have to upgrade (where we fixed the code) or reassess it to Low so npm audit won't crash. I suppose you could also patch npm audit so it doesn't crash.
• S

  Support for CocoaPods
  25 Apr 2024, 14:37 • stefan.kiryazov_8753   25 Apr 2024, 21:59

  2
  0
  Votes
  2
  Posts
  7
  Views

  25 Apr 2024, 21:59

  Hi @stefan-kiryazov_8753 , Thanks for the inquiry; I've updated our Other feed types docs with a link to this thread. On a first glance, it looks like a CocoaPod itself is just a basic text file that acts as a "pointer" to a GitHub repository. The pod client uses the git client to "download" files and tags for versioning. In other words, there is no package file. A CocoaPod repository is a Git repository, and the pod client seems to just use git client to commit/push files to the repo. In other words, there is no API for ProGet to implement. Here is what a CocoPod repo looks like (note how it's just a bunch of files in a Git repo): https://github.com/CocoaPods/Specs/tree/master/Specs To make a "private repo", you basically just create a Git repository: https://guides.cocoapods.org/making/private-cocoapods This means that ultimately to implement a CocoPods repository, your only option is to create a private Git repository? That's my inital assessment at least. And of course, we have no plans to add Git source code hosting to ProGet :) From here, I recommend to ask the developers to research this a bit more, and maybe contribute their thoughts? It just doesn't seem like the iOS devs uses packages - it's all very open-source and just GitHub repositories. Steve
• S

  ProGet: AD/LDAP issues with 2024 Docker image
  24 Apr 2024, 07:05 • scott.goodwin_8239   24 Apr 2024, 20:06

  3
  0
  Votes
  3
  Posts
  14
  Views

  S 24 Apr 2024, 20:06

  Thanks for the quick reply! I'll wait until the next build is released before testing the fix. Since I have a lot of other tasks on my plate right now, and the rollback to 2023 worked perfectly, there is no particular rush Cheers
• L

  Error Downloading Nuget Packages on Visual Studio
  24 Apr 2024, 18:50 • lucas.almeida_8120   24 Apr 2024, 19:45

  2
  0
  Votes
  2
  Posts
  9
  Views

  24 Apr 2024, 19:45

  Hi @lucas-almeida_8120, This a known issue that we are currently working through. It seems to be an issue with some bad/duplicate data in your database. The current workaround is to downgrade to ProGet 2023. We are hoping to have a fix ready soon. Thanks, Dan
• P

  3rd Party Repository Feed error
  18 Apr 2024, 11:59 • proget+markus.koban_7308   24 Apr 2024, 15:25

  6
  0
  Votes
  6
  Posts
  28
  Views

  24 Apr 2024, 15:25

  Hi @proget-markus-koban_7308, Thank you for all the extra detail. I was able to recreate this issue and fix it as part of, PG-2628. This fixed will be released this Friday in ProGet 2023.34 and 2024.1. Thanks, Rich
• V

  Warnings about a package in Diagostic Center without package name
  24 Apr 2024, 06:23 • v.makkenze_6348   24 Apr 2024, 06:34

  2
  0
  Votes
  2
  Posts
  5
  Views

  24 Apr 2024, 06:34

  Hi @v-makkenze_6348 , Thanks for the report; please ignore this, it should not be logged in the Diagnostic Center. It's addressed via PG-2625 in ProGet 2024.1 Cheers, Alana
• S

  ProGet New Vulnerability scanning removes ability to block a package
  22 Apr 2024, 06:23 • scott.wright_8356   23 Apr 2024, 23:30

  5
  0
  Votes
  5
  Posts
  15
  Views

  S 23 Apr 2024, 23:30

  Thank you very much for this, Alana. Very much appreciated.
• A

  Downgrade From 2024 - Assets Page - Unable to cast object of type 'System.Int32' to type 'System.Int64'
  22 Apr 2024, 18:59 • arlymac_7956   23 Apr 2024, 12:40

  5
  0
  Votes
  5
  Posts
  21
  Views

  A 23 Apr 2024, 12:40

  Good Morning, Unfortunately that did not work and I had to restore to a previous database backup and update the packages etc. Thanks
• Z

  Retention Rule for Asset Directory: Keep last N versions or filter by date
  19 Apr 2024, 09:30 • zs-dahe   23 Apr 2024, 07:58

  4
  0
  Votes
  4
  Posts
  26
  Views

  23 Apr 2024, 07:58

  Hi @zs-dahe , Thanks for clarifying, that makes sense; that's not really the use case we intended for asset directory versioning, it was mostly a simple way for asset-directory end-users (i.e. generally not ProGet admins) to fix the occasional delete/accident. It's redundant with back-up, but the idea was that it would save administrator time at the cost of a little disk space. Since it'd be such a large change on our end to rewrite this, it'd be best to wait until there's more demand. Perhaps you could just not use asset versioning , and allow your backup server to handle this? Typically back-up tools will already retain a certain number of past versions of files. Cheers, Alana
• R

  Some latest versions of Nuget packages not available in ProGet
  18 Apr 2024, 15:15 • rick.kramer_9238   19 Apr 2024, 02:23

  4
  0
  Votes
  4
  Posts
  12
  Views

  19 Apr 2024, 02:23

  Hi @rick-kramer_9238, I'm really not sure what the underlying issue is or how to troubleshoot :( NuGet dependency resolution is really complicated, and what you're saying is probably related. If you get a "package/version cannot be found" error from the NuGet client, it doesn't necessarily mean that the version isn't there... jsut that the dependency search wasn't successful. You can just look at the ProGet server to see what packages/versions are there. If it's in the UI, iut will be in the API. Cheers, Alana
• F

  Reset ProGet Admin Password via API
  18 Apr 2024, 08:33 • forbzie22_0253   18 Apr 2024, 11:30

  2
  0
  Votes
  2
  Posts
  17
  Views

  18 Apr 2024, 11:30

  Hi @forbzie22_0253 , For the Native API, you would pass in a base-64 encoded string value for byte[] values. Sorry that we don't have any examples; it's not a very friendly API, and we don't call it via JSON ourselves. Most users will configure LDAP or SAML, so so this isn't a big priority for us to document or create an API for as you can understand. If you find something that works, please do share it here :) Thanks, Alana
• S

  Package Latest Version not showing in All Versions
  18 Apr 2024, 05:44 • scott.wright_8356   18 Apr 2024, 06:59

  2
  0
  Votes
  2
  Posts
  12
  Views

  18 Apr 2024, 06:59

  Hi @scott-wright_8356 , This is unfortunately the consequence/downside with frequently-updated packages (like 2-3x daily updates of electron-to-chromium) and metadata caching. The underlying issue is that different metadata queries have different cache expirations, so the search queries (e.g. "electron-" or "electron-to" or "chromium", etc) will not line up with index queries (e.g. "list electron-to-chromium versions"). There is no solution to this, aside from changing durations or disabling caching. In general, we very strongly advise against developers "always using the latest version of packages they see", since that's a major attack vector for software supply chains. It also makes build reproducibility basically impossible and gives testing a headache. Instead, we encourage a package approval process where only approved packages are consumable by build servers, as opposed to whatever's the latest version on the net Best, Alana
• 

  Wrong debian apt documentation (web and app)
  20 Feb 2024, 11:27 • Scati   18 Apr 2024, 01:27

  4
  0
  Votes
  4
  Posts
  27
  Views

  18 Apr 2024, 01:27

  Hi @daniel-scati , Thanks for catching that! I have updated the documentation. Thanks, Rich
• 

  Incorrect packages count in Feeds page
  packages feeds • 19 Feb 2024, 08:39 • Scati   17 Apr 2024, 08:04

  4
  0
  Votes
  4
  Posts
  21
  Views

  17 Apr 2024, 08:04

  Just to give you a heads up. I'm already on version 2023.32 and it works like a charm. Thank you.
• V

  Error during upgrade
  15 Apr 2024, 20:28 • v.makkenze_6348   16 Apr 2024, 01:55

  3
  0
  Votes
  3
  Posts
  7
  Views

  16 Apr 2024, 01:55

  Hi @v-makkenze_6348 , This error can happen if you made certain changes to IIS configuration; in this case, you changed the name of the ProGet site in IIS to something else. That is not supported, so you will get this error. In general, we recommend moving away from IIS; this is because Microsoft no longer recommends using IIS for modern applications (.NET). And there is weird behavior like this. They only recommend it as a proxy server and legacy application server (Classic ASP, .NET Framework, etc).
• A

  An error occurred while retrieving rows.
  11 Apr 2024, 19:59 • akillen_5633   15 Apr 2024, 19:49

  5
  0
  Votes
  5
  Posts
  26
  Views

  A 15 Apr 2024, 19:49

  @atripp The sp_updatestats stored procedure resolved the issue for us. Really appreciate the assistance.
• J

  What is the general design philosophy regarding permissions and visibility in ProGet?
  3 Apr 2024, 16:17 • jw   15 Apr 2024, 14:01

  8
  0
  Votes
  8
  Posts
  44
  Views

  15 Apr 2024, 14:01

  Hi @jw , let's move some of these to a new thread, since this is sort of getting a bit long / off topic. I'll reply here then lock the thread, but feel free to reply as a new thread for any one of these topics. First, if you haven't already, I'd submit your database so we can test using your database. I don't know what has/hasn't been tested yet, but that's what we plan to do this week. Internal Ids --- we will likely not include internal Ids in the /sca endpoints; those are only exposed in the native API (which we don't recommend using). We really don't you to use the Native API since it arbitrarily changes. Docs -- the docs are going to be a little behind, but those will come out shortly after; note that our primary API will become a CLI, so the API docs will favor examples for pgutil. This will actually make building out new APIs a lot easier, since we can just point to GitHub code to show how it works, etc. SCA Events -- these will also trigger when you upload a noncompliant package and one is discovered in an overnight scan (either of packages or builds). This is our starting point from zero, so we'll see what feedback we have and adjust accordingly.