Support

• C

  Buy Weed in Edmonton Telegram @plughigh
  • cesarviagi_1715  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• J

  Creating Users with Native API
  • jipianu_mihnea_1277  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• C

  Buy Weed, coke in Montreal Telegram @plughigh
  • cesarviagi_1715  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• C

  Buy weed, cocaine Telegram @plughigh Toronto
  • cesarviagi_1715  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• U

  Proget - Feature Request - Package Upload
  • udi.moshe_0021  

  5
  0
  Votes
  5
  Posts
  16
  Views

  U

  @atripp , Guess you are right. thank you.
• C

  Buy weed, cannabis, in Berlin on Telegram @GreenlifeEU
  • cesarviagi_1715  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• C

  Buy weed, cannabis, Cork on Telegram @GreenlifeEU
  • cesarviagi_1715  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• E

  OCI support?
  helm oci • • edward.a.peng_7759  

  3
  1
  Votes
  3
  Posts
  16
  Views

  J

  In our case, we're not specifically looking for Proget to add a feed type that is a generic implementation of OCI, we are asking for the existing feed types to fully support OCI image and feed standards where applicable (container images, helm charts, SBOMs, etc). At the very least, for container and helm feeds. The specific purpose of OCI is ensuring compatibility and standardization across different platforms and tools. It appears Proget is now behind nearly every other product in this regard for these artifact types. Proget at the very least should support and preserve OCI schema elements related to each feed type: Proget Docker feeds should accept and preserve oci schema elements, example: artifactType on descriptors if supplied (introduced in 2023) mediaType(s): application/vnd.docker.distribution.manifest.v2+json as well as OCI Image Media Types Proget helmchart feeds should should accept and preserve oci schema elements, example: artifactType: application/vnd.cncf.helm.chart if supplied application/tar+gzip when using index.yaml for classic/ existing charts Helm OCI MediaTypes (used by default in Helm as of 3.8), or convert to OCI entirely since all of Helm is now on ArtifactHub.io (already supported by Proget as of 2024.17) Notable container registries already supporting the Open Container Initiative image and distribution specs: Azure Container Registry (ACR) added support 2023 Google Container Registry (GCR) transitioned to Google Artifact Registry (ACR) 2021-2024 Microsoft Container Registry (MCR) added support 2023 Amazon ECR added support 2020 GitLab Container Registry added support 2021 Artifactory added support 2023 OpenRegistry added support 2023 Docker Hub added support 2023 Zot (2020 OCI-only) Docker desktop builds vnd.oci.image.manifest.v1+json by default now, not vnd.docker.distribution.manifest.v2 Zot only supports vnd.oci.image.manifest OCI supports zstd and zstd:chunked. Not only is this a better compression format, which should speed up image pulls, zstd:chunked will allow container tools like Podman, Buildah and CRI-O to pull only the files that have changed in an image rather than the entire image. Buildah, a Red Hat tool, allows building (only OCI) container images without docker daemon as a requirement Beyond this subset of examples, it's becoming increasingly harder to find tools related to this space that haven't implemented OCI standards. Without OCI compliance in Proget container/ helm feeds, we're forced to look at other feed solutions that are keeping up with industry standards for proper tool interoperability. It seems like it would be a large win for Proget to implement OCI as a base, and extend that into the container (docker v2 images+feed schema are already OCI compatible), chart, sbom, and generic/ a (new) oci artifact feed type based on known OCI artifactType/mediaType definitions.
• L

  Unable to upload files to asset directories
  • layfield_8963  

  9
  0
  Votes
  9
  Posts
  23
  Views

  

  @layfield_8963 great news, that was a really strange error. The UI upload uses some kind of chunking and file appending, so it sounds like that was it.
• J

  Failed to fetch package tags for <local package name> from registry.npmjs.org.
  • janne.aho_4082  

  3
  0
  Votes
  3
  Posts
  9
  Views

  J

  Thanks for the reply, we on our end have to take a discussion and see if there is a budget increase option or if we just throttle traffic.
• E

  npm feed + nodejs.org connector: huge memory footprint and npm install ECONNRESETs
  • enrico+proget_8830  

  4
  0
  Votes
  4
  Posts
  27
  Views

  

  Hi @enrico-proget_8830, So we have fixed multiple issues with npm, specifically the npm connectors in the versions since you installed. I think upgrading to ProGet 2025.26 should resolve your issue with the ECONNRESET issue. Could you update to 2025.26 and rerun your test and let us know if you are still seeing the issue? Here is a link to the change list since your version of ProGet: https://my.inedo.com/downloads/upgrade?product=ProGet&fromVersion=2024.22 Thanks, Rich
• S

  ProGet: Auto package promotion from NuGet mirror?
  • scampbell_8969  

  8
  0
  Votes
  8
  Posts
  26
  Views

  

  @dan-brown_0128 thanks for clarifying 2500 is a lot more than I'm thinking... I was envisioning a handful of frequently-updated / highly-trusted packages (like AWSSDK, ). I think the UI would struggle a bit. Thinking about this further... a blanket "all future versions are OK" policy seems like it will cause more problems than benefits. That's a lot of decision-making burden to shift to developers, and they're just going to hit "update" the moment they're prompted. Best case scenario, that update delivers Zero Business Value... but there's a chance it'll introduce a regression, etc. I'd really need to study the data before recommending a practice like this (let adding a supported usecase for it) I'd be open to some sort of "automatic approval" feature, but I'd want to see some other factors in there, other than just "name matches X". As it stands, "package approval/promotion" isn't very widely used as it's solving a problem most organizations don't believe they have. Instead they drop $300K+ for Clownstrike or another security tool and believe it just "does everything for them". At that price, how could it not! So I think it's best to pin this for a bit. It's still a pretty "frontier" discussion/feature, and I don't want to "invent" something that's not going to get a lot of widespread use.
• J

  Otter server receives thousands of connections from agent after reboot
  otter agents bug • • jimbobmcgee  

  5
  0
  Votes
  5
  Posts
  16
  Views

  J

  @stevedennis I understand not wanting to go in blind on something so low-level. For what it is worth, the monkey-patch I applied has been stable, so far, in my lab environment. Let me know if you need me to test a build, prior to Otter 2025.
• S

  Working Rafts_CreateOrUpdateRaftItem example for Otter
  otter • • scusson_9923  

  18
  0
  Votes
  18
  Posts
  54
  Views

  S

  Hi Dean, Setting RaftItemType_Code = 7 in this instance worked for me. Appreciate the list of valid types. Thanks for all of your help! Scott
• 

  Creating a new PowerShell module
  • steviecoaster  

  4
  0
  Votes
  4
  Posts
  10
  Views

  

  Hi @steviecoaster, Thanks! We will take a look as soon as we can! Thanks, Rich
• E

  Conda feeds: some packages not visible in WebGUI
  • e.rotteveel_1850  

  4
  0
  Votes
  4
  Posts
  12
  Views

  E

  Thanks for the quick reply! We'll await the next release then.
• K

  Aggregating 2 Feeds in ProGet Free Edition
  • kc_2466  

  19
  0
  Votes
  19
  Posts
  65
  Views

  

  Looks like I had misunderstood the exact problem. One related issue was already fixed in 2024.25, but the aggregation issue with one connector having a package and another not having it was not. I have confirmed that both will be fixed in today's release of 2024.26, along with that Invalid Feed Type error. Sorry for the confusion!
• K

  Formatting issue on webpage for Cargo aggregate feed
  • kc_2466  

  2
  0
  Votes
  2
  Posts
  6
  Views

  

  @kc_2466 thanks for the heads up, we'll target reviewing/fixing this for the following maintenance release (i.e. 2024.27 / Feb 21) via PG-2893
• E

  Conda: Add "track_features" and "app_own_environment" to repodata.json output(s)
  • e.rotteveel_1850  

  6
  0
  Votes
  6
  Posts
  26
  Views

  

  We've added both of these properties to the index - you should see them in this week's release of 2024.26 on Friday. Thanks for the feature request!
• J

  "Log scope Execution has already been completed" exception after OSCall
  otter otterscript • • jimbobmcgee  

  2
  0
  Votes
  2
  Posts
  8
  Views

  

  Hi @jimbobmcgee , Thanks for all the details; we plan to review/investigate this via OT-518 in an upcoming maintenance release, likely in the next few two-week cycles. -- Dean