Project

General

Profile

Actions

Bug #24376

closed

build failed in compiling dashboard

Added by Xuehan Xu almost 6 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Recently, I found that the building process of ceph can't finish due to a npm error:

2600 silly pacote range manifest for set-value@^2.0.0 fetched in 851ms
2601 http fetch GET 200 https://registry.npmjs.org/to-object-path 855ms
2602 silly pacote range manifest for to-object-path@^0.3.0 fetched in 859ms
2603 http fetch GET 200 https://registry.npmjs.org/union-value 846ms
2604 silly pacote range manifest for union-value@^1.0.0 fetched in 855ms
2605 http fetch GET 200 https://registry.npmjs.org/unset-value 853ms
2606 http fetch GET 200 https://registry.npmjs.org/align-text 850ms
2607 silly pacote range manifest for unset-value@^1.0.0 fetched in 866ms
2608 silly pacote range manifest for align-text@^0.1.3 fetched in 865ms
2609 silly pacote range manifest for is-plain-object@^2.0.3 fetched in 3ms
2610 silly pacote range manifest for split-string@^3.0.1 fetched in 1ms
2611 silly pacote range manifest for set-value@^0.4.3 fetched in 3ms
2612 silly pacote range manifest for has-value@^0.3.1 fetched in 7ms
2613 http fetch GET 200 https://registry.npmjs.org/lazy-cache 845ms
2614 silly pacote range manifest for lazy-cache@^1.0.3 fetched in 847ms
2615 silly pacote range manifest for is-plain-object@^2.0.1 fetched in 1ms
2616 silly pacote range manifest for get-value@^2.0.3 fetched in 2ms
2617 http fetch GET 200 https://registry.npmjs.org/align-text 848ms
2618 silly pacote range manifest for align-text@^0.1.1 fetched in 850ms
2619 http fetch GET 200 https://registry.npmjs.org/math-random 845ms
2620 silly pacote range manifest for math-random@^1.0.1 fetched in 847ms
2621 http fetch GET 200 https://registry.npmjs.org/object-copy 853ms
2622 silly pacote range manifest for object-copy@^0.1.0 fetched in 856ms
2623 silly pacote range manifest for kind-of@^3.0.3 fetched in 2ms
2624 http fetch GET 200 https://registry.npmjs.org/map-visit 862ms
2625 silly pacote range manifest for map-visit@^1.0.0 fetched in 865ms
2626 http fetch GET 200 https://registry.npmjs.org/object-visit 846ms
2627 silly pacote range manifest for object-visit@^1.0.0 fetched in 848ms
2628 http fetch GET 200 https://registry.npmjs.org/has-values 859ms
2629 silly pacote range manifest for has-values@^1.0.0 fetched in 862ms
2630 silly pacote range manifest for kind-of@^4.0.0 fetched in 2ms
2631 http fetch GET 200 https://registry.npmjs.org/has-values 841ms
2632 silly pacote range manifest for has-values@^0.1.4 fetched in 843ms
2633 http fetch GET 200 https://registry.npmjs.org/longest 1071ms
2634 silly pacote range manifest for longest@^1.0.1 fetched in 1074ms
2635 http fetch GET 200 https://registry.npmjs.org/copy-descriptor 844ms
2636 silly pacote range manifest for copy-descriptor@^0.1.0 fetched in 846ms
2637 error cb() never called!
2638 error This is an error with npm itself. Please report this error at:
2639 error <https://github.com/npm/npm/issues>

I tried "npm cache clean -f", but it didn't work, the error remains.

Actions #1

Updated by Xuehan Xu almost 6 years ago

My OS is CentOS 7.4

Actions #2

Updated by Kefu Chai almost 6 years ago

  • Project changed from CephFS to mgr
Actions #3

Updated by Lenz Grimmer almost 6 years ago

  • Category set to 132
Actions #4

Updated by Ricardo Marques almost 6 years ago

Did you previously executed `npm install` with an `npm` version different than the one you are using now?

Try to remove `src/pybind/mgr/dashboard/frontend/node_modules` folder, may fix the problem.

Actions #5

Updated by Xuehan Xu almost 6 years ago

Ricardo Marques wrote:

Did you previously executed `npm install` with an `npm` version different than the one you are using now?

Try to remove `src/pybind/mgr/dashboard/frontend/node_modules` folder, may fix the problem.

Hi, It can't be built the first time I try to do so. And It seems that node_modules hadn't even been created.

Actions #6

Updated by Xuehan Xu almost 6 years ago

Um...It seems that this is due to my http proxy configuration after clearing which the building process resumed. Sorry for bothering you guy. Please feel free to close this issue.

Actions #7

Updated by Lenz Grimmer almost 6 years ago

  • Status changed from New to Closed

Thanks for the feedback! Closing as requested.

Actions #8

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 132 to General
Actions

Also available in: Atom PDF