Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Unable to connect to Telerik
-
We got rid of the error above by modifying the connector url by removing the trailing "/-/all". Now the feed indexing task succeeds, and npm install throws this error:
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-l10n/-/kendo-angular-l10n-0.3.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-dialog/-/kendo-angular-dialog-0.19.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-popup/-/kendo-angular-popup-0.17.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-upload/-/kendo-angular-upload-0.20.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-intl/-/kendo-angular-intl-0.12.0.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-buttons/-/kendo-angular-buttons-0.24.0.tgz -
Hello Yannick,
Telerik's repository isn't listing the publishing date of the packages, and ProGet is getting confused and assuming that means the packages were never published. This will be fixed in the next version of ProGet (4.7.11) [PG-1019]
-
Thanks, but will that solve the npm fetch error as well?
The paths seem to be unexisting:
/@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz -
Current situation:
- connector URL is https://registry.npm.telerik.com/ (before it was https://registry.npm.telerik.com/-/all)
- connector shows "Error"
- feed shows no error but no packages (before it was showing a "(404) Not Found" error)
- npm install shows errors (the paths seem to be invalid (404) or the tgz files are missing):
npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz
=> the path https://packages.tobania.be/npm/npm-telerik-proxy/@progress/kendo-data-query/ seems to produce some JSON content though that contains relatively built URL's like the tgz file URL above
-
Have you brought these issues to the attention of Telerik?
It's clear to me they wrote their own implementation of a proprietary npm registry, and I'm not keen on supporting their quirks in addition to all the npmjs.org quirks...
-
I already did and pointed them to this support question. Their reply: "We will log your feedback in our backlog and consider it when planning our future releases."
We get different errors now (500 instead of 404) during npm install:
npm ERR! fetch failed https://packages.tobania.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.2.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 500
npm ERR! fetch failed https://packages.tobania.be:443/npm/npm-telerik-proxy/@progress/kendo-theme-default/-/kendo-theme-default-2.31.3.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 500I'll let Telerik know.
PG-1019 doesn't seem to be solved:
Getting metadata from https://registry.npm.telerik.com/-/all
Finished downloading metadata. Indexing packages...
Error indexing @progress/kendo-angular-buttons: "modified" property on "time" is missing or invalid. -
Well.. if "making a npm registry that works with universal package managers" is not a priority for them, then I think continuing down this rabbithole is a pointles exercize.
I would suggest to just manually store their packages.
-
Alex,
The response Yannick received from Telerik is their generic response to pretty much every request. By no means are they saying supporting Universal Package Managers isn't a priority, they are a large company with many irons in the fire (like many others, ours included) so I'm sure it will be added to their list and prioritized how they see fit.
As corporate, paying users of your product, it is very important that we can use it with pretty much any feed (including Telerik’s). As such, we would greatly appreciate if someone from Inedo would contact Telerik directly to resolve any outstanding issues. If that is not an option, I would appreciate if someone would contact me directly to resolve the issue.
Thanks
-
Please understand that these issues are entirely on Telerik's end. Simply put, they did not implement a proper npm registry (feed). This is why it's not working in ProGet.
If they did, they would not be doing things like sending invalid index data (such packages without publish dates). We made a few small changes to try to get it working, but we can't keep adding special handling and work-arounds for Telerik's proprietary implementation.
We have no relationship with Telerik, so we can't contact them on our users' behalf. However, we would certainly welcome a dialog with them, and we've worked with Microsoft (to ensure NuGet keeps working w/ ProGet), as well as Telerik's competitors to ensure their private feeds work with private repository managers.
-
Thank you for your effort. Telerik is working on a long-term solution I understood.
-
Hi Yannick,
Did you see on a Telerik forum that they are looking at a long term solution?
-
Lucas, no I was told (I think unofficially) in a support ticket. They will announce it when they'd decide to go for it.
-
Team member here. I'd like to let you know that we've moved to the public npm registry.
See Retiring the Progress NPM Registry.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better đź’—
Register Login