[
https://issues.apache.org/jira/browse/FLINK-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428635#comment-17428635
]
Ingo Bürk commented on FLINK-24520:
-----------------------------------
It _could_ be
[frontend-maven-plugin#826|[https://github.com/eirslett/frontend-maven-plugin/issues/826].]
The not-so-satisfying solution there seems to have been the node version,
which would at least make sense because we've already observed that different
patch versions of node have varying levels of success depending on the platform.
> Building of WebUI failed on Ubuntu 20
> -------------------------------------
>
> Key: FLINK-24520
> URL: https://issues.apache.org/jira/browse/FLINK-24520
> Project: Flink
> Issue Type: Sub-task
> Components: Build System, Runtime / Web Frontend
> Affects Versions: 1.13.3
> Reporter: Chesnay Schepler
> Priority: Major
>
> While preparing the 1.13.3 release I ran into an issue where the WebUI could
> not be built via maven.
> {code}
> [INFO] husky > setting up git hooks
> [INFO] HUSKY_SKIP_INSTALL environment variable is set to 'true', skipping Git
> hooks installation.
> [ERROR] Aborted
> [ERROR] npm ERR! code ELIFECYCLE
> [ERROR] npm ERR! errno 134
> [ERROR] npm ERR! husky@1.3.1 install: `node husky install`
> [ERROR] npm ERR! Exit status 134
> [ERROR] npm ERR!
> [ERROR] npm ERR! Failed at the husky@1.3.1 install script.
> [ERROR] npm ERR! This is probably not a problem with npm. There is likely
> additional logging output above.
> {code}
> However, manually invoking npm from the command-line worked just fine.
> Deleting the node[_modules] directory had no effect.
> We should investigate what was causing these issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
