[
https://issues.apache.org/jira/browse/FLINK-18288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136307#comment-17136307
]
Yadong Xie edited comment on FLINK-18288 at 6/16/20, 5:28 AM:
--------------------------------------------------------------
[~appleyuchi]
plz note that :
# `node-sass/v4.11.0/linux-x64-72_binding.node` is not the static file, the
file position and name is determined by your npm and node version dynamically,
which means that it will always have an error if you have installed *unmatched*
node or npm version yourself. That is why *it works fine* in every other' and
ci environment except yours.(just imagine that you have installed many
different versions of maven and want them to work together in the same command
line, which is impossible.)
# the node and npm version are managed by maven-frontend-plugin in the
flink-runtime-web/pom.xml in isolated
folders(flink-runtime-web/web-dashboard/node and
flink-runtime-web/web-dashboard/node_modules), if you want to manage it
yourself(try to run npm ci or npm install yourself), *DON'T DO THIS* until you
have full knowledge of npm and node package, it would mess up the isolated env
of node and npm.
# plz have a try to remove all your `flink-runtime-web/web-dashboard/node` and
`flink-runtime-web/web-dashboard/node_modules` caches in the
flink-runtime-web/web-dashboard and have a try again.
was (Author: vthinkxie):
[~appleyuchi]
plz note that :
# `node-sass/v4.11.0/linux-x64-72_binding.node` is not the static file, the
file position and name is determined by your npm and node version dynamically,
which means that it will always have an error if you have installed *unmatched*
node or npm version yourself. That is why it works fine in every other' and ci
environment(just imagine that you have installed many different versions of
maven and want them to work together in the same command line, which is
impossible.)
# the node and npm version are managed by maven-frontend-plugin in the
flink-runtime-web/pom.xml in isolated
folders(flink-runtime-web/web-dashboard/node and
flink-runtime-web/web-dashboard/node_modules), if you want to manage it
yourself(try to run npm ci or npm install yourself), *DON'T DO THIS* until you
have full knowledge of npm and node package, it would mess up the isolated env
of node and npm.
# plz have a try to remove all your `flink-runtime-web/web-dashboard/node` and
`flink-runtime-web/web-dashboard/node_modules` caches in the
flink-runtime-web/web-dashboard and have a try again.
> WEB UI failure in Flink1.12
> ---------------------------
>
> Key: FLINK-18288
> URL: https://issues.apache.org/jira/browse/FLINK-18288
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.12.0
> Reporter: appleyuchi
> Priority: Major
>
>
>
> ①build command:
> *mvn clean install -T 2C -DskipTests -Dskip.npm -Dmaven.compile.fork=true*
>
> ②use flink-conf.yaml from 1.1o.1 in 1.12
> masters:
> Desktop:8082
>
> slaves:
> Desktop
> Laptop
> ③$FLINK_HOME/bin/start-cluster.sh
>
>
> ④open browser in:
> Desktop:8082
> {"errors":["Unable to load requested file /index.html."]}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
