Posts made by Jana.Rebmann_7461

Hi Rich,
I'll try what you suggested, thank you. We tried to upgrade NPM client, unfortunately this will use also a newer version of Node.js which has a different error handling that caused all our unit tests to break. So we skipped that option until all tests are fixed.
The issue appears since one year now. It disappeared for 2 or 3 months but always came back.

Thanks,
Jana

Hi Rich,

thanks for your feedback! We have no anti-virus or something running on these servers. I saw that suggestion (to disable it) also when researching in the past. We are using Atlassian Bamboo as build server and we have activated that it cleans up the directory after every build so there is no node_modules folder in the working directory.

Regarding your question the error appears sporadically. There are weeks where it doesn't appear in a single build and other weeks where it appears in every second build. We are tracking this issue now for a year and it disappears sometimes and appears again later. Unfortunately we didn't find any relation there.

Good point, I understand we could also experience that issue with npmjs.org when we use it for a while. I already tried running npm cache clean --force before starting to install the npm packages and also tried deleting the npm cache directory C:\Windows\System32\config\systemprofile\AppData\Roaming\npm-cache. It did not help... Do you have experience how I could make sure to delete the cache before installing npm packages or how to use a dedicated directory for the cache to make sure there is no link/access issue?

Thanks in advance.

Jana

Hi Rich,
thanks for the fast reply. I have send the log file to the support mail address with the ticket number you provided.

Thank you!
Jana

Hi all,
when installing npm packages from proget we regularly receive following error

Any ideas where this could come from and how to solve it?

• It appears in different environments (different servers, different build plans, different packages etc.).
• While investigating we changed the source to use the official npm registry instead of proget and it did not appear in 10 of 10 tries. When pulling the packages from proget it appeared in 7 of 12 tries. We already tried to disable antivirus programs, running as administrator etc.
• We are using Proget v5.3.31, Node v12 and npm v6.

@gdivis
I found the missing setting. It was in Manage Feed > Supported API. I selected "JSON-LD (v3)" and now all is fine.

As this setting was not automatically activated in Proget it would help in my opinion to add it in you docs https://docs.inedo.com/docs/proget-feeds-nuget-problems-with-my-nuget-org-connectors Currently it says If you have already upgrade to ProGet 5.3+, you are not affected by this.

Thank you,
Jana

@gdivis
Hi, thank's for the fast reply! I changed the URL as following:
nuget.exe restore Shiftconnector.sln -Source https://proget.eschbach.com/nuget/nuget-internal/v3/index.json

I think I'm still missing something, it tries to do a OData query from what I see:

17-Jun-2021 08:12:48WARNING: Unable to find version '3.1.0' of package 'NaturalSort.Extension'.
build 17-Jun-2021 08:12:48 C:\Windows\system32\config\systemprofile.nuget\packages: Package 'NaturalSort.Extension.3.1.0' is not found on source 'C:\Windows\system32\config\systemprofile.nuget\packages'.
build 17-Jun-2021 08:12:48 https://proget.eschbach.com/nuget/nuget-internal/v3/index.json: Unable to load the service index for source https://proget.eschbach.com/nuget/nuget-internal/v3/index.json.
build 17-Jun-2021 08:12:48 Response status code does not indicate success: 404 (OData method is not implemented.).

In proget I have the nuget connector configured with URL: https://api.nuget.org/v3/index.json

Hi,
we are using a nuget package which has metadata information in the version. It is NaturalSort.Extension 3.1.0+build.51. When installing nuget packages via nuget.exe an error appears which seems to find the package in proget but is not able to access it probably because of the metadata part in the file name.

GET https://proget.eschbach.com/nuget/nuget-internal/Packages(Id='NaturalSort.Extension',Version='3.1.0')
build 16-Jun-2021 10:34:24 OK https://proget.eschbach.com/nuget/nuget-internal/Packages(Id='NaturalSort.Extension',Version='3.1.0') 7ms
build 16-Jun-2021 10:34:24 GET https://proget.eschbach.com/nuget/nuget-internal/package/NaturalSort.Extension/3.1.0+build.51
build 16-Jun-2021 10:34:24 NotFound https://proget.eschbach.com/nuget/nuget-internal/package/NaturalSort.Extension/3.1.0+build.51 1ms
build 16-Jun-2021 10:34:24 WARNING: Unable to find version '3.1.0' of package 'NaturalSort.Extension'.

Additionally since the update to version 5.3.31 the service status page does not show any health checks anymore. How can I reactivate them?