-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default package push url now uses push subdomain #1285
Comments
To keep this from a breaking change, if someone has already configured an Apikey for the old push source, we will display a warning and tell them to change it, but use the old url. |
ferventcoder
added a commit
that referenced
this issue
May 18, 2017
Add checks to see if someone is using an old or new push source. If one of those is being used, display the warning about moderation.
ferventcoder
added a commit
that referenced
this issue
May 18, 2017
When pushing larger packages, the original push url was subject to a timeout of 100 seconds, a limitation of using Cloudflare. The error: `Error publishing package. NuGet server returned 524: Origin Time-out" when pushing through the Cloudflare infrastructure. Instead, convert to a new default push url that is not subject to a timeout by Cloudflare. To ensure this is not a breaking change, determine whether the old apikey was set and use it with a warning to change it over to use the new url.
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
May 18, 2017
* stable: Remove duplicate word (chocolateyGH-1285) Default push to new or old w/warning (chocolateyGH-1285) Add old/new default push source (chocolateyGH-1298) GenericRunner.count() sets security protocol (chocolateyGH-1298) GenericRunner.list() should match run() (maint) API - Warn on extraction errors (chocolateyGH-389) API - Ensure ChocolateyInstall env var (maint) Do not load config back into global (chocolateyGH-1296) API - Reuse existing base configuration (maint) API - Note methods that won't allow changes (chocolateyGH-1294) API - Expose container directly (build) option to build debug version (doc) Source/Key notes surrounding source/apikey (maint) log that license file has been found (chocolateyGH-1287) Non-internal SimpleInjector XML Comments (maint) formatting (chocolateyGH-1287) API - Ensure dll can work w/licensed code (chocolateyGH-1284) Install-ChocolateyPackage aliases File/File64
@ferventcoder I'm seeing this again, even on the new subdomain.
HTTP 524 is a CloudFlare-specific code, right? Did proxying for the push subdomain somehow get reenabled? |
@ferventcoder Please reopen this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cloudflare has a timeout of 100 seconds, which is sometimes not enough to get a package pushed up to the default community repo.
"Error publishing package. NuGet server returned 524: Origin Time-out"
This is to support https://github.com/chocolatey/chocolatey.org/issues/499 (the issue all the original references)
Ensure that the push does not timeout on Cloudflare's timeout.
The text was updated successfully, but these errors were encountered: