search

tobice / LDVMi

Visualization service for Payola Platform
Other
1 stars 1 forks source link

Unable to build #18

Closed jirihelmich closed 8 years ago

jirihelmich commented 8 years ago

LP-AppGen_Master_1.log.txt

tobice commented 8 years ago

It works smoothly with sbt dist. It only breaks when executed using activator. I will look into it.

tobice commented 8 years ago

It should be fixed now. For some reason, activator is way more sensitive to build.sbt file structure (missing or extra blank lines) compared to sbt.

jirihelmich commented 8 years ago

Yes, the build server picked up the commit and the build is running now.

jirihelmich commented 8 years ago

It's running, but it throws some flexbox css loading errors in the console. However, the university connection is very slow right now, so it might be that.

http://xrg12.projekty.ms.mff.cuni.cz:58080/appgen

You can try and if you see a problem, just commit into your repo, it should be deployed automatically within 5 minutes after the commit.

tobice commented 8 years ago

Thank you, this is great.

The problem is with the JavaScript bundle. For some reason, it is slightly different from the bundle I get when I compile it locally. Any chance I could access the build log? The npm output should be included.

jirihelmich commented 8 years ago

LP-AppGen_Master_3.log.txt

jirihelmich commented 8 years ago

What's the status? I see the same error. Need help?

tobice commented 8 years ago

I guess my e-mail got lost somewhere along the way.

The problem is with a rather archaic version of node and npm on the server. Some of the dependencies complain about it and refuse to compile. Do you think you could look into it?

My local setup (for which it's working) looks like this:

tobik@zenbook ~ $ npm --version
2.15.5
tobik@zenbook ~ $ node --version
v4.4.5
jirihelmich commented 8 years ago

Should be an easyfix, just say which version you need.

jirihelmich commented 8 years ago

Oh, sorry.

jirihelmich commented 8 years ago 
helmich@xrg12:~$ npm -v
1.4.14
helmich@xrg12:~$ node -v
v0.10.29

Well...

jirihelmich commented 8 years ago 
root@xrg12:~# npm -v
3.9.5
root@xrg12:~# node -v
v6.2.2
jirihelmich commented 8 years ago

Not sure it helped, though. The build finished and the problem persists.

tobice commented 8 years ago

I'm examining the log. It looks good, the errors are gone. Is it possible that the JS file is somewhere cached?

tobice commented 8 years ago

The log contains this:

[23:59:20][Step 1/3] ERROR in The `libsass` binding was not found in /usr/local/teamcity-agents/buildAgent/work/c53d396748485d82/src/node_modules/node-sass/vendor/linux-x64-48/binding.node
[23:59:20][Step 1/3] This usually happens because your node version has changed.
[23:59:20][Step 1/3] Run `npm rebuild node-sass` to build the binding for your current node version.

Do you think you could run npm rebuild node-sass for me?

jirihelmich commented 8 years ago

Done.

jirihelmich commented 8 years ago

It works.

tobice commented 8 years ago

Awesome.

Yeah, it was all caused by one annoying dependency which is actually not that important but it is the only one that requires SASS to work. I should have gotten rid of it long time ago.

Anyway, everything seems to be working, feel free to generate applications :) I used my import script so everything is ready and the sample data sources are there.

I'm only afraid that at this moment I will have time to fix only the most pressing issues.

jirihelmich commented 8 years ago

@jakubklimek, @martinnec: If you want, you can test the appgen as well at http://xrg12.projekty.ms.mff.cuni.cz:58080/appgen.