Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to exec soy script #802

Closed
oliosien opened this issue Apr 17, 2018 · 9 comments
Closed

Failed to exec soy script #802

oliosien opened this issue Apr 17, 2018 · 9 comments
Labels
comp: infrastructure They are used in problems that are related to monorepo infrastructure, build, process automation... resolution: duplicate Issues that are duplicates type: bug Issues reporting that Component is not doing what should be done

Comments

@oliosien
Copy link

I have executed npm run build, but I get this error (see attached file).

npm-debug.log

@jbalsas jbalsas added the type: bug Issues reporting that Component is not doing what should be done label Apr 17, 2018
@jbalsas
Copy link
Contributor

jbalsas commented Apr 17, 2018

Hi @oliosien, sorry you hit this... the first thing that comes to mind was, that you might not have Java installed, but I think I can see it in your PATH...

Can you confirm what OS are you running and what jdk version?

@oliosien
Copy link
Author

Hi @jbalsas, I have installed java version "1.8.0_151" and I work on Windows 10 station.

@kino90
Copy link

kino90 commented Apr 18, 2018

Hi @oliosien @jbalsas ,
I was having the same issues when trying to exec npm run build on my workspace (which is a Windows10 machine, with Node 8.0.0 and Java 1.8.0_141

It looks like Window can't handle RegExp as CLI arguments, so this line is failing:

metalsoy --soyDeps '../../node_modules/clay-+(button|icon)/src/**/*.soy'

The (button|icon) isn't getting parsed as a regExp by Windows system, resulting in the bash calling icon) as a command itself, and then returning an error like icon) is not a valid program

I solved building the project in a Linux VM, even if I'd rather this problem to be fixed soon to go back working on my workspace, instead of a vm

@jbalsas
Copy link
Contributor

jbalsas commented Apr 18, 2018

Hey @kino90, thanks so much for that tip! That helps narrowing this down a lot! We'll take a look at this soon!

@kino90
Copy link

kino90 commented Apr 18, 2018

Also, I had to install Java on my VM, which isn't written anywhere.. I took a while to guess it (until I read this issue) 😉

@jbalsas
Copy link
Contributor

jbalsas commented Apr 18, 2018

Yeah, I checked because I thought we mentioned that somewhere, but I couldn't find it, so I'll make sure we add a clear warning with this. Sorry for the trouble!

@oliosien
Copy link
Author

oliosien commented Apr 18, 2018

Thx to all

@carloslancha
Copy link
Contributor

@jbalsas @kino90 @oliosien is this still happening?

@matuzalemsteles matuzalemsteles added the comp: infrastructure They are used in problems that are related to monorepo infrastructure, build, process automation... label Nov 23, 2018
@matuzalemsteles
Copy link
Member

Hey guys, I'm closing this so we can track this down in question #1056 that is related.

@matuzalemsteles matuzalemsteles added the resolution: duplicate Issues that are duplicates label Nov 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp: infrastructure They are used in problems that are related to monorepo infrastructure, build, process automation... resolution: duplicate Issues that are duplicates type: bug Issues reporting that Component is not doing what should be done
Projects
None yet
Development

No branches or pull requests

5 participants