[ 
https://issues.apache.org/jira/browse/TEZ-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177718#comment-15177718
 ] 

Sreenath Somarajapuram edited comment on TEZ-3152 at 3/3/16 11:57 AM:
----------------------------------------------------------------------

Attaching a clean fix for both the issues.

#1 One of the dependent package (ember-cli-font-awesome), had a binding with 
the node version in use. The same was replaced with build script changes.

#2 async-disk-cache issue was fixed by forcing the build to use a local ./tmp 
directory (that we already use) instead of the global /tmp directory.

[~hitesh] please review.


was (Author: sreenath):
Attaching fix for both the issues.

#1 One of the dependent package (ember-cli-font-awesome), had a binding with 
the node version in use. The same was replaced with build script changes.

#2 async-disk-cache issue was fixed by forcing the build to use a local ./tmp 
directory (that we already use) instead of the global /tmp directory.

[~hitesh] please review.

> Tez UI 2: Build fails when run by multiple users or when node_modules is old
> ----------------------------------------------------------------------------
>
>                 Key: TEZ-3152
>                 URL: https://issues.apache.org/jira/browse/TEZ-3152
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3152.1.patch, TEZ-3152.wip.1.patch
>
>
> We have two separate cases in which the build fails:
> #1 The build uses Nodejs v0.12.2. When the webapp folder already have a 
> node_modules folder installed by an old version of node, build fails.
> - To repro, just manually run npm install in webapp with an old node (Like 
> v0.10.36). Then run mvn package from tez.
> #2 async-disk-cache package creates files in tmpDir (/tmp). When run from a 
> different user, because of user permission on there files, the build fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to