Posts made by parthu.reddy

Hi @atripp

We've created new feed with new connector and still getting this error.

Thanks
Parthu

Hi @atripp

We're using version 2025.8 and I've selected that box you mentioned during reindex. I'll run it one more time. If I run it one more time the issue related to UNIQUE KEY will also be fixed right?

Can you also explain us why this error is occurring for this package and how it resulted in this corrupted state.

JFI - in our sand environment we're not facing this issue for this package.

Thanks
Parthu

We're getting following error while trying to access this package. Pls suggest

Hi @atripp

We found that as we're running 3 clustered servers behind haproxy(load balancer) these chunked data is sent to different servers and resulting in file being used by another process error.

We've changed the load balancing to sticky and all chunks are going through single server resulting in successful upload.

I believe this has to be fixed by proget. Could you look into it.

Thanks
Parthu

Hi Team

We've created a docker feed with DockerHub connector but couldn't find below image.

https://hub.docker.com/r/microsoft/dotnet-runtime/

Pls suggest on this.

Thanks
Parthu

Hi @stevedennis

Can we know how we could enable verbose logging to check for any connectivity failures.

Thanks
Parthu

Hi Team

Currently we're on proget 2024.37. Could we do proget upgrade to 2025 without doing maven classic to maven new migration. We would like to do this migration after moving to 2025.8. Pls suggest.

Thanks
Parthu

Hi Team,

Proget is showing deleted versions of nuget packages.

https://www.nuget.org/packages/System.ComponentModel.Composition#versions-body-tab

Can you confirm if it's a bug.

Thanks
parthu

Hi Team

We're using proget 2024.37 (Build 4) and trying to upload .spd files to an assets, and we're getting error like below.

We've checked with our firewall team and they mentioned this.

Pls suggest on this.

Thanks
Parthu

Hi Team

We've recently upgraded to 2024.37 to improve performance of proget. We've thousands of error like this.

And lot of errors like this.

Very few of these.


Almost all of them related to npm. Could you suggest on this.

Thanks
parthu

Hi Team

The question might be basic but need this info. Can we know the maximum number of requests that proget can handle at a time. I'm asking for active requests that could be processed, not the queue.

We're using IIS for running proget.

Thanks
Parthu

Hi Team

We've upgraded to latest version 2024.37 and got following error while testing. Should we be worried about this.

Thanks
Parthu

Hi @stevedennis / @atripp

We're getting lot of these errors after removing the cache configuration

Why are we getting connection pool error when there's no connection pool?

Thanks
Parthu

Hi @stevedennis

Thanks for the info.

Another question, where is this metadata-caching stored? On the proget server or in DB?

Why I'm asking is, if we add new server to cluster, does this cause increase in requests to nuget.org if the caching is done on server locally?

Does this metadata caching feature reduce the queries to fetch versions that you mentioned?

And can I get links to this caching. Does this

Thanks
Parthu

Hi @stevedennis

Just need some more info. What is the configured time for timeout. Are you maintaining any connection pool for number of connections to nuget.

Thanks
Parthu

Hi Steve

Thanks for the info. A question, normally proget fetches from connector if a package is not available locally right. In this case is it trying to download new package and has timeout or some network issue? If that's the case what can it fetch from cached copy?

Is it possible to know what it's requesting for.

Thanks
Parthu

Hi Team

Recently we got too many of these warnings. Can we know when this occurs.

Thanks
Parthu

Hi @atripp

Actually we created a license WTGBL and assigned it to a package that doesn't have any license. and the packages that have this license should be noncompliant.

So when we try to download it shouldn't we stop it without downloading even for first time.

And our team suggested that if some license type are only known after downloading full package, it would be possible to discard those without saving. Is this possible to do from your end?

Why this is needed:
Our security team told that there are few files on the machine that doesn't meet security standards. And few versions of this package shouldn't be available on the machine itself.

Thanks
Parthu

Previously we were able to block packages for specific version but now we don't see that option.

Why has this been removed?

Thanks
Parthu

Hi Team

We created a License WTGBL so that it blocks few log4j-core versions from being downloaded. But when we do that it's not stopping the package from being downloaded for the first time. After that it's blocked.

Proget version: 2024.13

Thanks

A small question, can we upgrade proget but continue using classic maven for some time

@dean-houston Thanks

@dean-houston

https://repo1.maven.org/maven2/com/sun/activation/jakarta.activation/2.0.0-RC2/jakarta.activation-2.0.0-RC2.pom

Getting error for jakarta.activation-2.0.0 versions

Looks like there's some problem in orginal repo itself

Another example:
https://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-parent/3.0.0/jaxb-parent-3.0.0.pom

I'm getting few of these errors.

An empty feed is getting this error

Getting this error while moving from classic maven to new maven on 2024.22

We've 3 proget servers in cluster, during upgrade do we have to stop all 3 servers and then do upgrade or can we do upgrade one server after another without stopping other servers.

Thanks

@dean-houston Thanks

Steps to reproduce:

1. Upgrade from 2024.13 to 2024.22
2. Upgrade classic maven feed to new maven feed
3. Revert back to classic maven feed
4. Downgrade from 2024.22 to 2024.13
5. Try accessing connectors page
   You'll get above error.

Could you pls look into it. If we've some problems and if we want to downgrade it's better if such issues doesn't occur.

Thanks

After renaming the feed the API keys are pointing to maven old feed. Should this be done manually. If so I think it's better if it's mentioned in documentation as well.

https://docs.inedo.com/docs/proget/feeds/maven#maven-classic-feed-types

Pls let us know your thoughts. If there are any such cases, pls let us know.

Every time I run dotnet tool run paket restore --verbose I'm getting error with different packages. It's not the same every time I run it. Could you let us know why this is happening.

We came across this while trying to upgrade from 2024.6 to 2024.13. So we again downgraded it to 2024.6 and checked there. Looks like it's happening in both the versions.

Any reason why whole database is locked?

Looks like it's starting with this.

Getting lot of these errors, could you suggest on this.

Thanks, we're planning to upgrade tomorrow. Will keep you updated.

Yes @stevedennis , that would be helpful. Pls ship it early.

Thanks

And our team suggested that increasing VARCHAR(50) to a larger number for versions in Maven tables could help. Could you check it.

If it's not possible, could you let us know an eta on fixing this.

@stevedennis said in File not found org.scala-sbt.jline/jline:

2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493

In the above screenshot, there is a version without 3 in it, is it created by proget? When I clicked that version, the files inside it are same as the one with 3

Versions that are on maven doesn't match the versions that are on proget.
Getting 2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c096450749 extra version on proget.

https://repo1.maven.org/maven2/org/scala-sbt/jline/jline/2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493/jline-2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493.pom - maven pom url

http://proget.sand.wtg.zone/maven2/Maven-Sbt/org/scala-sbt/jline/jline/2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c096450749/jline-2.14.7-sbt-a1b0ffbb8f64bb820f4f84a0c07a0c0964507493.pom - proget pom url, looks like 3 is missing.

This is happening in version 2024.5, after upgrading from 2024.3.

Deleted the artifact, now not able to find any packages in versions.

@atripp Ohh, sorry my mistake, changed it to proget, same problem actually. Will check at our end.

@atripp Thanks

Actually it's just postman to trigger APIs, pls check the versions. I triggered multiple versions, All of them got immediate response except for the 1.3.1 and 1.3.0. These two versions are failing sometimes. Will check with wireshark, pls check at your end as well.(there might be possibilities of missing headers that helps in closing socket or something like that.)

Actually this has nothing to do with npm client I guess. As I'm directly downloading the tgz from proget, which was causing error in npm client.

Getting this error for only 1.3.1 and 1.3.0 versions. others are working fine. Any idea why?

This is happening randomly.

Got this error. Could you check this.

Version 2024.3 (Build 4) - this is the version

getting
This artifact cannot be downloaded because it is Noncompliant: Artifact does not have an associated .pom.
error for a lot of maven repositories.

https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-project/3.1.2/hadoop-project-3.1.2.pom

I understand that there is some parsing problem with POM file but it can be downloaded I guess, as SHA1 and MD5 are valid.

Let us know your thoughts.