汽车日报 汽车日报

当前位置: 首页 » 汽车资讯 »

比亚迪f3仪表灯图解

比亚迪f3里程表显示fail啥意思?

这里有两种方式,

第一种:电脑硬件系统恢复出厂设置,如下步骤:

1.把电脑关机后在开机,或者重启,启动时按DEL键。

2.出现这个画面就按DEL键电脑就会跳转到BIOS界面。

3.右下角的optimizedDefauits就是出厂最佳参数,点击快捷键f3就会跳转倒下一个界面。

4.这时点击ENTER键确定,系统就会恢复出厂设置了。

5.记得要点击save&exit对应的快捷键f4(保存更改并退出)。

扩展资料:

BIOS芯片中主要存放:

1.自诊断程序:通过读取CMOSRAM中的内容识别硬件配置,并对其进行自检和初始化;

2.CMOS设置程序:引导过程中,用特殊热键启动,进行设置后,存入CMOS RAM中;

3.系统自举装载程序:在自检成功后将磁盘相对0道0扇区上的引导程序装入内存,让其运行以装入DOS系统;

4.主要I/O设备的驱动程序和中断服务:由于BIOS直接和系统硬件资源打交道,因此总是针对某一类型的硬件系统,而各种硬件系统又各有不同,所以存在各种不同种类的BIOS,随着硬件技术的发展,同一种BIOS也先后出现了不同的版本,新版本的BIOS比起老版本来说,功能更强。

第二种,windows操作系统恢复出厂,步骤如下

2、找到并点击“更新和安全”。

3、点击“恢复”。

4、点击“开始”。

5、在弹出的对话框中,选择是"保留我的文件"还是“删除所有内容”,确认后点击选项,电脑就开始恢复出厂设置。

扩展资料

出厂设置恢复到出厂时的默认状态,如开始界面,待机方式,操作快捷键,定时提醒等功能恢复,清除保存的参数设置。

将设备或仪器的个性设置恢复到出厂的默认状态,如开始界面,待机方式,操作快捷键,定时提醒等等恢复到出厂时的设置但不会删除存储的数据。

啟動修復無法自動修復這電腦

台式电脑可以恢复到出厂设置的,具体方法如下:   1、将电脑关机然后开机或者直接点击重启,然后按住"DELETE"键,这时,电脑会自动进入到BIOS。   2、电脑屏幕上会显示两个选项(两个选项一般都在电脑屏幕的右方)。   3、其中一个选项是“Load Fail-Safe Defaults”选项(系统预设的稳定参数)。再一个选项是“Load Optimized Defaults”(系统预设的最佳参数)。   4、选择“Load Optimized Defaults”选项:用方向键选中该选项,然后点击回车确定,这时系统会出现提示,点Y键,再次回车确定。最后别忘了保存之前的设置:点“Save&exit step”或者按F10。

Redis集群报错cluster_state:fail,如何解决并重新恢复集群

Redis集群报错cluster_state:fail,如何解决并重新恢复集群(IP问题/ slot未完全分配问题)

报错

127.0.0.1:6379> set name tom ---》测试在redis集群中存数据时报错-> Redirected to slot [5798] located at 192.168.3.2:6379(error) CLUSTERDOWN The cluster is down192.168.3.2:6379> cluster infocluster_state:fail ---》显示集群状态已关闭cluster_slots_assigned:16384cluster_slots_ok:10923cluster_slots_pfail:0cluster_slots_fail:5461cluster_known_nodes:6cluster_size:3cluster_current_epoch:6cluster_my_epoch:2cluster_stats_messages_ping_sent:2203cluster_stats_messages_pong_sent:392cluster_stats_messages_meet_sent:4cluster_stats_messages_fail_sent:4cluster_stats_messages_sent:2603cluster_stats_messages_ping_received:391cluster_stats_messages_pong_received:310cluster_stats_messages_meet_received:1cluster_stats_messages_fail_received:1cluster_stats_messages_received:703解决

?查看所有redis日志发现redis-5容器一直在反复连接192.168.3.1:6379这个master节点node-1

[root@es-node22 ~]# docker logs -f redis-5......1:S 28 May 2022 13:07:53.233 # Cluster state changed: fail1:S 28 May 2022 13:07:53.442 * Connecting to MASTER 192.168.3.1:63791:S 28 May 2022 13:07:53.442 * MASTER <-> REPLICA sync started1:S 28 May 2022 13:07:53.442 # Error condition on socket for SYNC: Connection refused1:S 28 May 2022 13:07:54.481 * Connecting to MASTER 192.168.3.1:63791:S 28 May 2022 13:07:54.481 * MASTER <-> REPLICA sync started......

?查看node-1的redis节点配置文件redis.conf中的节点IP

[root@es-node22 ~]# cat /root/redis/node-1/conf/redis.confport 6379bind 0.0.0.0cluster-enabled yescluster-config-file nodes.conf ---》redis集群节点配置文件cluster-node-timeout 5000cluster-announce-ip 192.168.3.11 ---》可以看到node-1节点配置文件中IP为192.168.3.11cluster-announce-port 6379cluster-announce-bus-port 16379appendonly yes

?查看当前的redis集群状态,以数组形式展示

192.168.3.2:6379> cluster slots ---》当前的集群状态,以数组形式展示1) 1) (integer) 10923 2) (integer) 16383 3) 1) "192.168.3.3" 2) (integer) 6379 3) "ff0d1d636f94d9b092e6012408c1d0918e00e6ed" 4) 1) "192.168.3.4" 2) (integer) 6379 3) "2113cf366ad27ebd73585f03d368e77f03b1a2e1"2) 1) (integer) 0 2) (integer) 5460 3) 1) "192.168.3.1" ---》可以看到集群中该节点的IP是192.168.3.1 2) (integer) 6379 3) "c856c94ba8d2c55a0d176831bc85aa34a96fde88" 4) 1) "192.168.3.5" 2) (integer) 6379 3) "d92ff5984ab29370af0adeaca71e7938c0287ca5"3) 1) (integer) 5461 2) (integer) 10922 3) 1) "192.168.3.2" 2) (integer) 6379 3) "8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3" 4) 1) "192.168.3.6" 2) (integer) 6379 3) "2108a90495c147c675328f9b8b4fa49e2b856faf"

?查看redis集群节点配置文件nodes.conf

[root@es-node22 ~]# cat /root/redis/node-1/data/nodes.confc856c94ba8d2c55a0d176831bc85aa34a96fde88 192.168.3.1:6379@16379 myself,master - 0 1653743266000 1 connected 0-5460d92ff5984ab29370af0adeaca71e7938c0287ca5 192.168.3.5:6379@16379 slave c856c94ba8d2c55a0d176831bc85aa34a96fde88 0 1653743274000 5 connected2108a90495c147c675328f9b8b4fa49e2b856faf 192.168.3.6:6379@16379 slave 8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 0 1653743275531 6 connected2113cf366ad27ebd73585f03d368e77f03b1a2e1 192.168.3.4:6379@16379 slave ff0d1d636f94d9b092e6012408c1d0918e00e6ed 0 1653743275531 4 connected8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 192.168.3.2:6379@16379 master - 0 1653743275531 2 connected 5461-10922ff0d1d636f94d9b092e6012408c1d0918e00e6ed 192.168.3.3:6379@16379 master - 0 1653743275000 3 connected 10923-16383vars currentEpoch 6 lastVoteEpoch 0[root@es-node22 ~]# cat /root/redis/node-2/data/nodes.confff0d1d636f94d9b092e6012408c1d0918e00e6ed 192.168.3.3:6379@16379 master - 0 1653743273233 3 connected 10923-163832113cf366ad27ebd73585f03d368e77f03b1a2e1 192.168.3.4:6379@16379 slave ff0d1d636f94d9b092e6012408c1d0918e00e6ed 0 1653743271151 4 connectedc856c94ba8d2c55a0d176831bc85aa34a96fde88 192.168.3.1:6379@16379 master,fail - 1653743267074 1653743266961 1 connected 0-5460d92ff5984ab29370af0adeaca71e7938c0287ca5 192.168.3.5:6379@16379 slave c856c94ba8d2c55a0d176831bc85aa34a96fde88 0 1653743272000 1 connected8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 192.168.3.2:6379@16379 myself,master - 0 1653743271000 2 connected 5461-109222108a90495c147c675328f9b8b4fa49e2b856faf 192.168.3.6:6379@16379 slave 8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 0 1653743272194 6 connectedvars currentEpoch 6 lastVoteEpoch 0

?可以看到redis所有节点的集群配置文件nodes.conf中是192.168.3.1:6379,与node-1节点的redis.conf文件中不一致。

?批量修改所有redis节点nodes.conf文件中该节点IP配置

[root@es-node22 ~]# for i in $(seq 1 6); do \> sed -i 's/192.168.3.1/192.168.3.11/' /root/redis/node-${i}/data/nodes.conf> done

?查看修改后的所有redis集群nodes.conf文件

[root@es-node22 ~]# cat /root/redis/node-1/data/nodes.conf c856c94ba8d2c55a0d176831bc85aa34a96fde88 192.168.3.11:6379@16379 myself,master - 0 1653743266000 1 connected 0-5460d92ff5984ab29370af0adeaca71e7938c0287ca5 192.168.3.5:6379@16379 slave c856c94ba8d2c55a0d176831bc85aa34a96fde88 0 1653743274000 5 connected2108a90495c147c675328f9b8b4fa49e2b856faf 192.168.3.6:6379@16379 slave 8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 0 1653743275531 6 connected2113cf366ad27ebd73585f03d368e77f03b1a2e1 192.168.3.4:6379@16379 slave ff0d1d636f94d9b092e6012408c1d0918e00e6ed 0 1653743275531 4 connected8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 192.168.3.2:6379@16379 master - 0 1653743275531 2 connected 5461-10922ff0d1d636f94d9b092e6012408c1d0918e00e6ed 192.168.3.3:6379@16379 master - 0 1653743275000 3 connected 10923-16383vars currentEpoch 6 lastVoteEpoch 0[root@es-node22 ~]# cat /root/redis/node-2/data/nodes.confff0d1d636f94d9b092e6012408c1d0918e00e6ed 192.168.3.3:6379@16379 master - 0 1653743273233 3 connected 10923-163832113cf366ad27ebd73585f03d368e77f03b1a2e1 192.168.3.4:6379@16379 slave ff0d1d636f94d9b092e6012408c1d0918e00e6ed 0 1653743271151 4 connectedc856c94ba8d2c55a0d176831bc85aa34a96fde88 192.168.3.11:6379@16379 master,fail - 1653743267074 1653743266961 1 connected 0-5460d92ff5984ab29370af0adeaca71e7938c0287ca5 192.168.3.5:6379@16379 slave c856c94ba8d2c55a0d176831bc85aa34a96fde88 0 1653743272000 1 connected8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 192.168.3.2:6379@16379 myself,master - 0 1653743271000 2 connected 5461-109222108a90495c147c675328f9b8b4fa49e2b856faf 192.168.3.6:6379@16379 slave 8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 0 1653743272194 6 connectedvars currentEpoch 6 lastVoteEpoch 0......

?批量重启redis集群所有节点容器

[root@es-node22 ~]# docker restart $(docker ps | grep redis | awk '{print $1}')dcd802a160c66e2f628457f6f05d3dfb9c8b220df78836e931e7b232f1d11de91b4d4e68[root@es-node22 ~]# docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES6e2f628457f6 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6376->6379/tcp, :::6376->6379/tcp, 0.0.0.0:16376->16379/tcp, :::16376->16379/tcp redis-6f05d3dfb9c8b redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6375->6379/tcp, :::6375->6379/tcp, 0.0.0.0:16375->16379/tcp, :::16375->16379/tcp redis-5220df78836e9 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6374->6379/tcp, :::6374->6379/tcp, 0.0.0.0:16374->16379/tcp, :::16374->16379/tcp redis-431e7b232f1d1 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6373->6379/tcp, :::6373->6379/tcp, 0.0.0.0:16373->16379/tcp, :::16373->16379/tcp redis-31de91b4d4e68 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6372->6379/tcp, :::6372->6379/tcp, 0.0.0.0:16372->16379/tcp, :::16372->16379/tcp redis-2dcd802a160c6 redis:5.0.9-alpine3.11 "docker-entrypoint.s…" 3 hours ago Up 2 hours 0.0.0.0:6371->6379/tcp, :::6371->6379/tcp, 0.0.0.0:16371->16379/tcp, :::16371->16379/tcp redis-1

?重新查看redis集群状态

[root@es-node22 ~]# docker exec -it redis-1 /bin/sh ---》redis中默认没有bash解释器/data # redis-cli -c127.0.0.1:6379> cluster infocluster_state:ok ---》可以看到redis集群状态已经为OKcluster_slots_assigned:16384cluster_slots_ok:16384cluster_slots_pfail:0cluster_slots_fail:0cluster_known_nodes:6cluster_size:3cluster_current_epoch:6cluster_my_epoch:1cluster_stats_messages_ping_sent:236cluster_stats_messages_pong_sent:233cluster_stats_messages_sent:469cluster_stats_messages_ping_received:233cluster_stats_messages_pong_received:232cluster_stats_messages_received:465127.0.0.1:6379> cluster nodesc856c94ba8d2c55a0d176831bc85aa34a96fde88 192.168.3.11:6379@16379 master - 0 1653752958838 1 connected 0-54608b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 192.168.3.2:6379@16379 myself,master - 0 1653752957000 2 connected 5461-109222113cf366ad27ebd73585f03d368e77f03b1a2e1 192.168.3.4:6379@16379 slave ff0d1d636f94d9b092e6012408c1d0918e00e6ed 0 1653752957804 4 connected2108a90495c147c675328f9b8b4fa49e2b856faf 192.168.3.6:6379@16379 slave 8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3 0 1653752957086 6 connectedff0d1d636f94d9b092e6012408c1d0918e00e6ed 192.168.3.3:6379@16379 master - 0 1653752958000 3 connected 10923-16383d92ff5984ab29370af0adeaca71e7938c0287ca5 192.168.3.5:6379@16379 slave c856c94ba8d2c55a0d176831bc85aa34a96fde88 0 1653752958529 1 connected127.0.0.1:6379> cluster slots1) 1) (integer) 5461 2) (integer) 10922 3) 1) "192.168.3.2" 2) (integer) 6379 3) "8b01b1bc6202e1dc7ff9f15013d8200b10ecb3f3" 4) 1) "192.168.3.6" 2) (integer) 6379 3) "2108a90495c147c675328f9b8b4fa49e2b856faf"2) 1) (integer) 0 2) (integer) 5460 3) 1) "192.168.3.11" ---》可以看到集群中该节点的IP已经为修改后的IP 2) (integer) 6379 3) "c856c94ba8d2c55a0d176831bc85aa34a96fde88" 4) 1) "192.168.3.5" 2) (integer) 6379 3) "d92ff5984ab29370af0adeaca71e7938c0287ca5"3) 1) (integer) 10923 2) (integer) 16383 3) 1) "192.168.3.3" 2) (integer) 6379 3) "ff0d1d636f94d9b092e6012408c1d0918e00e6ed" 4) 1) "192.168.3.4" 2) (integer) 6379 3) "2113cf366ad27ebd73585f03d368e77f03b1a2e1"另一种情况

?当集群报错cluster_state:fail时,也有可能是因为slot未完全分配的问题导致集群不可用。因为redis为了保证集群完整性, 默认情况下当集群16384个槽任何一个没有指派到节点时,整个redis集群都会不可用。这是对集群完整性的一种保护措施, 保证所有的槽都指派给在线的redis节点。这种情况时,重新分配这些slots即可解决集群不可用问题。

如果您喜欢本文,就请动动您的发财手为本文点赞评论转发,让我们一起学习更多运维相关知识,最后请记得关注我。

突传噩耗!传奇大佬去世

4月7日晚间,沪电股份公告称,公司创办人、原董事长吴礼淦,于2024年4月4日与世长辞,享年83岁。

500亿A股原董事长逝世

A股上市公司沪电股份公告称,公司创办人、原董事长吴礼淦,于2024年4月4日与世长辞,享年83岁。沪电股份表示,吴礼淦的逝世不会导致公司实际控制人发生实质变化。

沪电股份在讣告中表示,吴礼淦先生于1992年创立公司前身昆山沪士电子有限公司,秉持“成长、长青、共利”的经营理念,勤勉敬业,守正创新,带领公司长期持续健康发展。公司董事、监事、高级管理人员及全体员工对吴礼淦先生的辛勤付出和卓越贡献致以最崇高的敬意,对吴礼淦先生的逝世表示沉痛哀悼和深切缅怀。

官网显示,沪电股份是一家从事半导体行业的公司,于1992年在江苏省昆山市设立,并于2010年在深圳证券交易所中小企业板挂牌上市。截至最新收盘报29.62元/股,市值566亿元。

刚辞职不到10天

就在3月28日晚间,沪电股份才公告宣布吴礼淦辞任公司董事长一职,公告称,董事会于2024年3月28日收到董事长吴礼淦先生的辞呈。因年事已高,吴礼淦先生辞去公司董事长、董事及在董事会下设专门委员会的职务。

印刷电路版业界的传奇人物

据公共报道,吴礼淦,是印刷电路版业界的传奇人物。当初他背着“棉花大王”的家世背景,毅然出来创立PCB工厂,已是当时一绝。之后他顶着压力,来到昆山市建厂,成立沪士电子有限公司。

<img data-imgfileid="505508837" data-ratio="0.671067106710671" data-s="300,640" data-src="?wx_fmt=png&from=appmsg&tp=wxpic&wxfrom=5&wx_lazy=1&wx_co=1" data-type="png" data-w="909" data-original-style="vertical-align: middle;font-family: system-ui, -apple-system, BlinkMacSystemFont, " helvetica="" neue",="" "pingfang="" sc",="" "hiragino="" sans="" gb",="" "microsoft="" yahei="" ui",="" yahei",="" arial,="" sans-serif;font-size:="" 16px;letter-spacing:="" 0.544px;text-align:="" center;text-wrap:="" wrap;background-color:="" rgb(255,="" 255,="" 255);outline:="" 0px;width:="" 643.146px="" !important;visibility:="" visible="" !important;"="" data-index="10" src="" _width="643.146px" crossorigin="anonymous" data-fail="0" data-mce-src="/a/10001/202404/89381604b5652a1e88f1b64e7e34a287.png" data-origin-src="" data-mce-attachid="3741800" data-mce-alias="640?wx_fmt=png&from=appmsg&wxfrom=5&wx_lazy=1&wx_co=1&" width="800">

2020年2月,吴礼淦家族以100亿元人民币财富名列《2020胡润全球富豪榜》第2000位。

2021年10月,吴礼淦家族以65亿元财富位列《2021年胡润百富榜》第1123名。

2022年11月,吴礼淦家族以55亿元财富位列《2022年胡润百富榜》第1127名。

从1997年起公司连续6年获外经贸部颁发的“双优企业”称号。财报显示,沪电股份2023年全年公司实现营业收入89.38亿元,同比增长7.23%;实现归母净利润15.13亿元,同比增长11.09%。2023年第四季度实现营收28.56亿元,环比增长23.15%;实现归母净利润5.59亿元,环比增长21.50%。

(据洪观新闻)

【NPM】cnpm无法打包问题解决

测试环境有一个需要 SonarQube 扫描的前端项目一直打包都是好好的,但是今天突然无法使用 cnpm run build 进行打包,上去服务器上面看看究竟报了什么样的错误。

既然本来打包的环境有问题,那么先干掉 node_modules 和 package-lock.json 再重新用 cnpm install 试试,得出如下结果。

[root@node6 yunlu-portals-sonar]# cnpm install? [13/26] Installing @babel/core@^7.11.0platform unsupported @vue/cli-plugin-babel@4.5.19 ? webpack@4.46.0 ? watchpack@1.7.5 ? chokidar@3.5.3 ? fsevents@~2.3.2 Package require os(darwin) not compatible with your platform(linux)[fsevents@~2.3.2] optional install error: Package require os(darwin) not compatible with your platform(linux)? [15/26] Installing js-yaml@^3.13.1platform unsupported @vue/cli-plugin-babel@4.5.19 ? webpack@4.46.0 ? watchpack@1.7.5 ? watchpack-chokidar2@2.0.1 ? chokidar@2.1.8 ? fsevents@^1.2.7 Package require os(darwin) not compatible with your platform(linux)[fsevents@^1.2.7] optional install error: Package require os(darwin) not compatible with your platform(linux)? [15/26] Installing javascript-stringify@^2.0.1[vue-loader-v16@npm:vue-loader@^16.1.0] optional install error: Error: Unsupported URL Type: npm:vue-loader@^16.1.0at parseUrl (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/npm-package-arg/npa.js:186:13)at npa (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/npm-package-arg/npa.js:79:12)at _install (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/npminstall/lib/install.js:62:11)at _install.next (<anonymous>)at onFulfilled (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/co/index.js:65:19)at /usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/co/index.js:54:5at new Promise (<anonymous>)at co (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/co/index.js:50:10)at toPromise (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/co/index.js:118:63)at next (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/co/index.js:99:29)......[5/11] scripts.postinstall image-webpack-loader@7.0.1 ? imagemin-pngquant@9.0.2 ? pngquant-bin@^6.0.0 run "node lib/install.js", root: "/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_pngquant-bin@6.0.1@pngquant-bin"pngquant pre-build test passed successfully[5/11] scripts.postinstall image-webpack-loader@7.0.1 ? imagemin-pngquant@9.0.2 ? pngquant-bin@^6.0.0 finished in 651ms[6/11] scripts.postinstall image-webpack-loader@7.0.1 ? imagemin-mozjpeg@9.0.0 ? mozjpeg@^7.0.0 run "node lib/install.js", root: "/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_mozjpeg@7.1.1@mozjpeg"Command failed: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_mozjpeg@7.1.1@mozjpeg/vendor/cjpeg -version/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_mozjpeg@7.1.1@mozjpeg/vendor/cjpeg: /lib64/libz.so.1: version `ZLIB_1.2.9' not found (required by /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_mozjpeg@7.1.1@mozjpeg/vendor/cjpeg)mozjpeg pre-build test failedcompiling from sourceError: Command failed: /bin/sh -c autoreconf -fiv/bin/sh: autoreconf: command not foundat Promise.all.then.arr (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/_execa@0.7.0@execa/index.js:231:11)at process._tickCallback (internal/process/next_tick.js:68:7)[npminstall:runscript:error] image-webpack-loader@7.0.1 ? imagemin-mozjpeg@9.0.0 ? mozjpeg@^7.0.0 scripts.postinstall run "node lib/install.js" error: RunScriptError: Run "sh -c node lib/install.js" error, exit code 1? Install fail! RunScriptError: post install error, please remove node_modules before retry!Run "sh -c node lib/install.js" error, exit code 1RunScriptError: post install error, please remove node_modules before retry!Run "sh -c node lib/install.js" error, exit code 1at ChildProcess.proc.on.code (/usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/runscript/index.js:96:21)at ChildProcess.emit (events.js:189:13)at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)npminstall version: 3.28.1npminstall args: /usr/local/node-v10.15.3-linux-x64/bin/node /usr/local/node-v10.15.3-linux-x64/lib/node_modules/cnpm/node_modules/npminstall/bin/install.js --fix-bug-versions --china --userconfig=/root/.cnpmrc --disturl= --registry=

按照输出报错来看其实并不能找到太多有用的信息,既然第一部分报错出现最多提示的是

[fsevents@~2.3.2] optional install error: Package require os(darwin) not compatible with your platform(linux)

那我们不用 cnpm 直接用 npm install 来试试吧(当然了需要先将 node_modules 和 package-lock.json 干掉)。

[root@node6 yunlu-portals-sonar]# npm install......> node-sass@4.14.1 install /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass> node scripts/install.jsUnable to save binary /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/vendor/linux-x64-64 : { Error: EACCES: permission denied, mkdir '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/vendor' at Object.mkdirSync (fs.js:752:3) at sync (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mkdirp/index.js:74:13) at Function.sync (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mkdirp/index.js:80:24) at checkAndDownloadBinary (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/scripts/install.js:114:11) at Object.<anonymous> (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/scripts/install.js:157:1) at Module._compile (internal/modules/cjs/loader.js:701:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10) at Module.load (internal/modules/cjs/loader.js:600:32) at tryModuleLoad (internal/modules/cjs/loader.js:539:12) at Function.Module._load (internal/modules/cjs/loader.js:531:3) errno: -13, syscall: 'mkdir', code: 'EACCES', path: '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/vendor' }> yorkie@2.0.0 install /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie> node bin/install.jssetting up Git hooks{ Error: EACCES: permission denied, open '/root/.jenkins/workspace/yunlu-portals-sonar/.git/hooks/applypatch-msg' at Object.openSync (fs.js:438:3) at Object.writeFileSync (fs.js:1189:35) at write (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie/src/install.js:18:6) at createHook (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie/src/install.js:60:5) at /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie/src/install.js:86:21 at Array.map (<anonymous>) at installFrom (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie/src/install.js:83:10) at Object.<anonymous> (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie/bin/install.js:24:1) at Module._compile (internal/modules/cjs/loader.js:701:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10) errno: -13, syscall: 'open', code: 'EACCES', path: '/root/.jenkins/workspace/yunlu-portals-sonar/.git/hooks/applypatch-msg' }> core-js@2.6.12 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/babel-runtime/node_modules/core-js> node -e "try{require('./postinstall')}catch(e){}"......gyp ERR! configure error gyp ERR! stack Error: EACCES: permission denied, mkdir '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/.node-gyp'gyp ERR! System Linux 3.10.0-1160.59.1.el7.x86_64gyp ERR! command "/usr/local/node-v10.15.3-linux-x64/bin/node" "/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="gyp ERR! cwd /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sassgyp ERR! node -v v10.15.3gyp ERR! node-gyp -v v3.8.0gyp ERR! not ok Build failed with error code: 1......npm ERR! code ELIFECYCLEnpm ERR! errno 1npm ERR! node-sass@4.14.1 postinstall: `node scripts/build.js`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the node-sass@4.14.1 postinstall script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2022-10-25T06_32_21_501Z-debug.log......

虽然使用 npm 已经没有了“Package require os(darwin) not compatible with your platform(linux)”问题,但是又出现了一个新的问题而且大部分都是由于 node-sass@4.14.1 爆出的。其中突破口在于“stack Error: EACCES: permission denied, mkdir '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/.node-gyp'”这一句话,明明我都已经使用了 root 账号来进行 npm 操作的了,为什么还是说我“permission denied”?

后来上网查阅了多篇文章发现原来npm是存在生命周期的,基于安全起见会进行自动降级处理,因此需要通过--unsafe-perm参数来进行解锁。npm 在执行前会按照顺序读取配置信息:cli -> env -> npmrc -> default(按照现公司的做法应该是没有配置的,因此推断最终是会读取 default 的配置),针对 unix 平台,使用 root 用户执行 npm 命令时 --unsafe-perm 得到的默认值都会是 false,这里应该手动设置为 true 或者在 npm install 时加入。

[root@node6 yunlu-portals-sonar]# npm install --unsafe-permnpm WARN deprecated axios@0.20.0: Critical security vulnerability fixed in v0.21.1. For more information, see WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.......> node-sass@4.14.1 install /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass> node scripts/install.jsDownloading binary from download "": ETIMEDOUTTimed out attemping to establish a remote connectionHint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g. export HTTP_PROXY=:1234or configure npm proxy via npm config set proxy :8080> yorkie@2.0.0 install /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/yorkie> node bin/install.jssetting up Git hooksdone> core-js@2.6.12 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/babel-runtime/node_modules/core-js> node -e "try{require('./postinstall')}catch(e){}"Thank you for using core-js ( ) for polyfilling JavaScript standard library!The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > > Also, the author of core-js ( ) is looking for a good job -)> core-js@3.26.0 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/core-js> node -e "try{require('./postinstall')}catch(e){}"Thank you for using core-js ( ) for polyfilling JavaScript standard library!The project needs your help! Please consider supporting of core-js:> > > bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz Also, the author of core-js ( ) is looking for a good job -)> ejs@2.7.4 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/ejs> node ./postinstall.jsThank you for installing EJS: built with the Jake JavaScript build tool ()> node-sass@4.14.1 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass> node scripts/build.jsBuilding: /usr/local/node-v10.15.3-linux-x64/bin/node /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=gyp info it worked if it ends with okgyp verb cli [ '/usr/local/node-v10.15.3-linux-x64/bin/node',gyp verb cli '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp/bin/node-gyp.js',gyp verb cli 'rebuild',gyp verb cli '--verbose',gyp verb cli '--libsass_ext=',gyp verb cli '--libsass_cflags=',gyp verb cli '--libsass_ldflags=',gyp verb cli '--libsass_library=' ]gyp info using node-gyp@3.8.0gyp info using node@10.15.3 | linux | x64gyp verb command rebuild []gyp verb command clean []gyp verb clean removing "build" directorygyp verb command configure []gyp verb check python checking for Python executable "python2" in the PATHgyp verb `which` succeeded python2 /usr/bin/python2gyp verb check python version `/usr/bin/python2 -c "import sys; print "2.7.5gyp verb check python version .%s.%s" % sys.version_info[:3];"` returned: %jgyp verb get node dir no --target version specified, falling back to host node version: 10.15.3gyp verb command install [ '10.15.3' ]gyp verb install input version string "10.15.3"gyp verb install installing version: 10.15.3gyp verb install --ensure was passed, so won't reinstall if already installedgyp verb install version not already installed, continuing with install 10.15.3gyp verb ensuring nodedir is created /root/.node-gyp/10.15.3gyp verb created nodedir /root/.node-gypgyp http GET http 200 verb extracted file from tarball include/node/common.gypigyp verb extracted file from tarball include/node/config.gypigyp verb extracted file from tarball include/node/node.h......gyp verb tarball done parsing tarballgyp verb check download content checksum, need to download `SHASUMS256.txt`... gyp verb checksum url http GET http 200 verb checksum data {"node-v10.15.3-aix-ppc64.tar.gz":"f2f018418b6bfa263ec981f04f3fa5337724edae8d77fc3951cd36667ee720ea","node-v10.15.3-darwin-x64.tar.gz":"7a5eaa1f69614375a695ccb62017248e5dcc15b0b8edffa7db5b52997cf992ba","node-v10.15.3-darwin-x64.tar.xz":"8e3df823a58c7b2de327540a0b57a9bcf3f706108fe65c4cde9a073caae68cee","node-v10.15.3-headers.tar.gz":"9e97ee69072836bfbf2a85c4af627ed152574c30c5a32e40fbfcdfda8d9b562e","node-v10.15.3-headers.tar.xz":"f690b8808ccfeb5959436073717b648e4bdc521e3217ab7092d5c033326f6133","node-v10.15.3-linux-arm64.tar.gz":"c82cd99e01f6e26830f0b3e0465f12f92957ebd69a68c91c03228c2669104359","node-v10.15.3-linux-arm64.tar.xz":"3d7abbf64bffb07c55168ca0f1c17be12b0d93affe9b6cadd39724649215fab9","node-v10.15.3-linux-armv6l.tar.gz":"72529b6f77d95f9422f6d1c6b88c1f921b00e5500a1c3ea05927f1ae3704133d","node-v10.15.3-linux-armv6l.tar.xz":"94432c2944fc78c2d5e82103f73596a060451330839562c04c414067007c5997","node-v10.15.3-linux-armv7l.tar.gz":"6958551264884cd479f15ed8d40673655a283ed3bd8552d04e8531cd3ccdf483","node-v10.15.3-linux-armv7l.tar.xz":"af2106b08f68e0884caa505ea7e695facc5b4cd356f1e08258899e94cc4c5df0","node-v10.15.3-linux-ppc64le.tar.gz":"0544b08467384ba3b3a462d8907d12cea71ac371f3d118057905dd845be43aad","node-v10.15.3-linux-ppc64le.tar.xz":"a2fcc2e1827d7a034f39aad8225b4dd72376ad19f7a7884645a512aeeedf4ab5","node-v10.15.3-linux-s390x.tar.gz":"073e6e2ad4e3a7580d87e5b70b9c1ce785b15e849dfd4f2f846c3039ad1e116c","node-v10.15.3-linux-s390x.tar.xz":"545caa31bf06b150861ca3a2b1f5112aa92bb855de20fd98f8b7bc3f4c4311d7","node-v10.15.3-linux-x64.tar.gz":"6c35b85a7cd4188ab7578354277b2b2ca43eacc864a2a16b3669753ec2369d52","node-v10.15.3-linux-x64.tar.xz":"faddbe418064baf2226c2fcbd038c3ef4ae6f936eb952a1138c7ff8cfe862438","node-v10.15.3.pkg":"f4d0b944618afae2835b500e0cc1c5a013912597fce5560cd4bcb534f5270754","node-v10.15.3-sunos-x64.tar.gz":"c678b8e5a2d652f920c1093e6249b08e4746c2d37a5b9f719d04f3243776fb01","node-v10.15.3-sunos-x64.tar.xz":"3732ae66ad564c192ff3a4a6e66e0d8922823c128bb8a6766ece87226982ad54","node-v10.15.3.tar.gz":"db460a63d057ac015b75bb6a879fcbe2fefaaf22afa4b6f6445b9db61ce2270d","node-v10.15.3.tar.xz":"4e22d926f054150002055474e452ed6cbb85860aa7dc5422213a2002ed9791d5","node-v10.15.3-win-x64.7z":"9df98cac063229aca443c040fd342a96667891bb8eda821d10aa4d49347d7add","node-v10.15.3-win-x64.zip":"93c881fdc0455a932dd5b506a7a03df27d9fe36155c1d3f351ebfa4e20bf1c0d","node-v10.15.3-win-x86.7z":"597a372964252daaba4cb8dcac57305f79cffeeca579625f0cd6ab85d29ccdda","node-v10.15.3-win-x86.zip":"fc28bbd08b3d9b621c7c0ecd2b42506ca2f356f31f2b64210f413b34cff31799","node-v10.15.3-x64.msi":"46b3d03c96de0b9e7d3a204c67772759283221f5e58ac225df813076a65e2738","node-v10.15.3-x86.msi":"e73398cde3e054da7a0a05a86aa512a47a24b961b0659be30a0f01606ca234a9","win-x64/node.exe":"a921d1a4fa463e877087b3f25abd0ab05b63489bffcc9ff47acbbeee4e1b7494","win-x64/node.lib":"4ed045ae1ba046506948b8f90c02716178cb0084f3b56866ac8d23b591e83235","win-x64/node_pdb.7z":"538c8cc4e0b93facb9d63ed6c55d765ec33a18dd264c6c8b9415ad242521d8e6","win-x64/node_pdb.zip":"525ea4adfd5c166076b273db6c0803283c57c4116fce56229ce87c8eb9fcdd25","win-x86/node.exe":"39efb2a884d2f73680b986534eed000017ce16993ea9d695351593ffb9a7bb34","win-x86/node.lib":"efed715422fcb7032290ec3c7e3b324126e082ee3a87d6ac497f6c97549e478e","win-x86/node_pdb.7z":"38775185b6f6c090e7039ea0b3e630f4ab83e5c259d8d94f0f35f04ec12c0e98","win-x86/node_pdb.zip":"1848e05e130dda3c3b53830cb78c4b28c137c7aac0890b70a8c863798c332ed5"}gyp verb download contents checksum {"node-v10.15.3-headers.tar.gz":"9e97ee69072836bfbf2a85c4af627ed152574c30c5a32e40fbfcdfda8d9b562e"}gyp verb validating download checksum for node-v10.15.3-headers.tar.gz (9e97ee69072836bfbf2a85c4af627ed152574c30c5a32e40fbfcdfda8d9b562e == 9e97ee69072836bfbf2a85c4af627ed152574c30c5a32e40fbfcdfda8d9b562e)gyp verb get node dir target node version installed: 10.15.3gyp verb build dir attempting to create "build" dir: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/buildgyp verb build dir "build" dir needed to be created? /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/buildgyp verb build/config.gypi creating config filegyp verb build/config.gypi writing out config file: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/build/config.gypigyp verb config.gypi checking for gypi file: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/config.gypigyp verb common.gypi checking for gypi file: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/common.gypigyp verb gyp gyp format was not specified; forcing "make"gyp info spawn /usr/bin/python2gyp info spawn args [ '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp/gyp/gyp_main.py',gyp info spawn args 'binding.gyp',gyp info spawn args '-f',gyp info spawn args 'make',gyp info spawn args '-I',gyp info spawn args '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/build/config.gypi',gyp info spawn args '-I',gyp info spawn args '/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp/addon.gypi',gyp info spawn args '-I',gyp info spawn args '/root/.node-gyp/10.15.3/include/node/common.gypi',gyp info spawn args '-Dlibrary=shared_library',gyp info spawn args '-Dvisibility=default',gyp info spawn args '-Dnode_root_dir=/root/.node-gyp/10.15.3',gyp info spawn args '-Dnode_gyp_dir=/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-gyp',gyp info spawn args '-Dnode_lib_file=/root/.node-gyp/10.15.3/<(target_arch)/node.lib',gyp info spawn args '-Dmodule_root_dir=/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass',gyp info spawn args '-Dnode_engine=v8',gyp info spawn args '--depth=.',gyp info spawn args '--no-parallel',gyp info spawn args '--generator-output',gyp info spawn args 'build',gyp info spawn args '-Goutput_dir=.' ]gyp verb command build []gyp verb build type Releasegyp verb architecture x64gyp verb node dev dir /root/.node-gyp/10.15.3gyp verb `which` succeeded for `make` /usr/bin/makegyp info spawn makegyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]make: Entering directory `/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/build' g++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.5.5"' -I/root/.node-gyp/10.15.3/include/node -I/root/.node-gyp/10.15.3/src -I/root/.node-gyp/10.15.3/deps/openssl/config -I/root/.node-gyp/10.15.3/deps/openssl/openssl/include -I/root/.node-gyp/10.15.3/deps/uv/include -I/root/.node-gyp/10.15.3/deps/zlib -I/root/.node-gyp/10.15.3/deps/v8/include -I../src/libsass/include -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++1y -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast.o.d.raw -c -o Release/obj.target/libsass/src/libsass/src/ast.o ../src/libsass/src/ast.cpp g++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.5.5"' -I/root/.node-gyp/10.15.3/include/node -I/root/.node-gyp/10.15.3/src -I/root/.node-gyp/10.15.3/deps/openssl/config -I/root/.node-gyp/10.15.3/deps/openssl/openssl/include -I/root/.node-gyp/10.15.3/deps/uv/include -I/root/.node-gyp/10.15.3/deps/zlib -I/root/.node-gyp/10.15.3/deps/v8/include -I../src/libsass/include -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++1y -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o.d.raw -c -o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o ../src/libsass/src/ast_fwd_decl.cpp ...... g++ -shared -pthread -rdynamic -m64 -Wl,-soname=binding.node -o Release/obj.target/binding.node -Wl,--start-group Release/obj.target/binding/src/binding.o Release/obj.target/binding/src/create_string.o Release/obj.target/binding/src/custom_function_bridge.o Release/obj.target/binding/src/custom_importer_bridge.o Release/obj.target/binding/src/sass_context_wrapper.o Release/obj.target/binding/src/sass_types/boolean.o Release/obj.target/binding/src/sass_types/color.o Release/obj.target/binding/src/sass_types/error.o Release/obj.target/binding/src/sass_types/factory.o Release/obj.target/binding/src/sass_types/list.o Release/obj.target/binding/src/sass_types/map.o Release/obj.target/binding/src/sass_types/null.o Release/obj.target/binding/src/sass_types/number.o Release/obj.target/binding/src/sass_types/string.o Release/obj.target/src/sass.a -Wl,--end-group rm -rf "Release/binding.node" && cp -af "Release/obj.target/binding.node" "Release/binding.node"make: Leaving directory `/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/build'gyp info ok Installed to /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/node-sass/vendor/linux-x64-64/binding.node> cwebp-bin@5.1.0 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/cwebp-bin> node lib/install.js ? Command failed: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/cwebp-bin/vendor/cwebp -version/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/cwebp-bin/vendor/cwebp: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory ? cwebp pre-build test failed ? compiling from source ? cwebp built successfully> gifsicle@5.2.1 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/gifsicle> node lib/install.jsgifsicle pre-build test passed successfully> mozjpeg@7.1.1 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mozjpeg> node lib/install.jsCommand failed: /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mozjpeg/vendor/cjpeg -version/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mozjpeg/vendor/cjpeg: /lib64/libz.so.1: version `ZLIB_1.2.9' not found (required by /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/mozjpeg/vendor/cjpeg)mozjpeg pre-build test failedcompiling from sourceError: Command failed: /bin/sh -c autoreconf -fiv/bin/sh: autoreconf: command not found at Promise.all.then.arr (/root/.jenkins/workspace/yunlu-portals-sonar/node_modules/bin-build/node_modules/execa/index.js:231:11) at process._tickCallback (internal/process/next_tick.js:68:7)> optipng-bin@7.0.1 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/optipng-bin> node lib/install.js(node:50697) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limitoptipng pre-build test passed successfully> pngquant-bin@6.0.1 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/pngquant-bin> node lib/install.jspngquant pre-build test passed successfully> swiper@6.8.4 postinstall /root/.jenkins/workspace/yunlu-portals-sonar/node_modules/swiper> node -e "try{require('./postinstall')}catch(e){}"Love Swiper? Support Vladimir's work by donating or pledging: > On Patreon > On Open Collective notice created a lockfile as package-lock.json. You should commit this file.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: vue-loader-v16@npm:vue-loader@^16.1.0 (node_modules/@vue/cli-service/node_modules/vue-loader-v16):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Invalid dependency type requested: aliasnpm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})npm WARN vue-awesome-swiper@4.1.1 requires a peer of swiper@^5.2.0 but none is installed. You must install peer dependencies yourself.npm WARN @vue/cli-service@4.5.19 requires a peer of @vue/compiler-sfc@^3.0.0-beta.14 but none is installed. You must install peer dependencies yourself.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mozjpeg@7.1.1 (node_modules/mozjpeg):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mozjpeg@7.1.1 postinstall: `node lib/install.js`npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1added 1807 packages from 747 contributors in 218.88s

npm install成功了之后就可以对项目进行编译

[root@node6 yunlu-portals-sonar]# npm run build--test> yunlu-pc@0.1.0 build--test /root/.jenkins/workspace/yunlu-portals-sonar> vue-cli-service build --mode test WARN A new version of sass-loader is available. Please upgrade for best experience.? Building for test... WARNING Compiled with 27 warnings 2:44:00 PMModule Warning (from ./node_modules/eslint-loader/index.js):/root/.jenkins/workspace/yunlu-portals-sonar/src/App.vue 54:11 warning Unexpected console statement no-console? 1 problem (0 errors, 1 warning)......Module Warning (from ./node_modules/thread-loader/dist/cjs.js):/root/.jenkins/workspace/yunlu-portals-sonar/src/utils/request.js 30:5 warning Unexpected console statement no-console 181:7 warning Unexpected console statement no-console? 2 problems (0 errors, 2 warnings) @ ./src/main.js 19:0-38 22:22-29 23:26-33 24:24-31 25:21-28 26:21-28 27:24-31 @ multi ./src/main.js warning asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).This can impact web performance.Assets: assets/img/collageBack.21c63be2.png (382 KiB) assets/img/1.81e7b71c.jpeg (572 KiB) assets/img/5.0d5efaf0.png (539 KiB) assets/img/3.4b8911f9.jpeg (936 KiB) assets/js/chunk-vendors.8cb38fe5.js (925 KiB) assets/js/chunk-vendors.8cb38fe5.js.gz (251 KiB) warning entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.Entrypoints: app (1.26 MiB) assets/css/chunk-vendors.b7a1ac8e.css assets/js/chunk-vendors.8cb38fe5.js assets/css/app.90f70f38.css assets/js/app.a3a124b8.js File Size Gzipped dist/assets/js/chunk-vendors.8cb38fe5.js 925.10 KiB 251.98 KiB ...... dist/assets/css/chunk-5c262660.9214b722.css 0.06 KiB 0.08 KiB Images and other types of assets omitted. DONE Build complete. The dist directory is ready to be deployed. INFO Check out deployment instructions at

未经允许不得转载: 汽车日报 » 比亚迪f3仪表灯图解

相关文章

themebetter

contact