![]() ![]() (C:\Program WARN old lockfile Could not fetch metadata for FetchError: Invalid response body while trying to fetch : ENOENT: no such file or directory, lstat 'D:\a\1. Npm WARN old lockfile at C:\Program Files\nodejs\node_modules\npm\node_modules\minipass-fetch\lib\body.js:162:15 task: 'npm | "$(Agent.OS)" | $(clientApp)\package-lock.json'īoth Cache npm and npm ci looks successful but looking at npm ci it is full of Invalid response body while trying to fetch errors. Npm_config_cache: $(Pipeline.Workspace)/.npm This results in the following output from the archive task: task: ne(variables.NPMZIP_CACHE_RESTORED, 'true')ĪrchiveFile: $(npm_config_cache)-archive\cache.zip WorkingDirectory: $(Build.SourcesDirectory)/PatternLibrary/ # Force config to a known, local folder that has (hopefully) been pre-filled. task: ne(variables.NPMZIP_CACHE_RESTORED, 'false')ĪrchiveFilePatterns: $(npm_config_cache)-archive\cache.zip task: 'npmzip | "$(Agent.OS)" | $(Build.SourcesDirectory)/PatternLibrary/package-lock.json' Partial hits should still see some performance gains. # need to manually unpack and pack the archive. # To work around this we manually archive the cache folder and cache that instead. # There appears to be an issue with the way the cache task creates archives and npm's cache format. cypress cache folder, which we are using in the same pipeline is being cached without any problem. ![]() npm folder before upload, then uploaded 100% of chunks of data. Some deduplication and archive optimization process must treat those files as possible to compress/deduplicate and thus results in stripped archive. npm folder structure (_cacache folder to be precise) which contains hashes as folder and files names. It uploads only ~20% in my case of all npm modules. Go Ahead She Isn't Looking MOTHERLESS.COM. Motherless has a very large and active community where you can meet like minded individuals. ![]() After some investigation it seems like task has problem with uploading tarballed archive with. is a moral free file host where anything legal is hosted forever. npm folder (similar to unfortunately closed without resolution issue: #12121), either by using default %AppData%\npm-cache or setting npm_config_cache environment variable. I have noticed the problem with caching npm-cache/. If using private agent, provide the OS of the machine running the agent and the agent version: windows-2019.Entering this information will route you directly to the right team and expedite traction. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |