chocolatey / package-validator

Windows service to validate packages conform to package standards
Apache License 2.0
31 stars 29 forks source link

Automated validation: timeout issue on URL #229

Closed chtof closed 4 years ago

chtof commented 4 years ago

https://chocolatey.org/packages/eclipse-java-oxygen/2020.03: eclipse-java-oxygen has failed automated validation. (...) The ProjectSourceUrl element in the nuspec file should be a valid Url. Please correct this

ProjectSourceUrl: https://git.eclipse.org/c

The project source URL is available so I think it's a timeout issue (the timeout was increased some time ago by Chocolatey Team but not sure if it has been applied on all URL tags). I have had this same issue with another package one or two day ago, I will post more information if I found the name of the another package.

chtof commented 4 years ago

Same issue for:

pauby commented 4 years ago

@chtof This issue is around the Package Validator so I'm going to move it to that repository.

chtof commented 4 years ago

Same issue also for:

chtof commented 4 years ago

https://chocolatey.org/packages/klog/1.0 The MailingListUrl element in the nuspec file should be a valid Url. Please correct this Software mailing list: https://www.klog.xyz/mailing-lists/

AdmiringWorm commented 4 years ago

Having the same problem with the audacity package, it mentions invalid URLs for DocsUrl, LicenseUrl and ProjectUrl.

All three of these URLs are valid though: https://www.audacityteam.org/help/documentation https://audacityteam.org/about/license#license https://audacityteam.org/

/CC @gep13 @pauby

gep13 commented 4 years ago

@AdmiringWorm for your issue, this seems to be a security feature of Cloudflare, which is preventing the URL's from being validated. See here:

image

We will add additional handling for this specific case.

gep13 commented 4 years ago

@chtof looks like re-running the package validator on some of your URL's, things are now "just" working. I think going forward, the correct course of action will be to re-try package validation prior to doing further investigation.

gep13 commented 4 years ago

@chtof @AdmiringWorm I believe everything has been taken care of here, so going to close this out. Let me know if you have any follow up comments.