Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Return of Grunt JS build errors #648

Open
harperaa opened this issue Aug 6, 2018 · 2 comments
Open

Return of Grunt JS build errors #648

harperaa opened this issue Aug 6, 2018 · 2 comments

Comments

@harperaa
Copy link

harperaa commented Aug 6, 2018

I installed from master on virgin 16.04, last week, in multi-install prod configuration. All was well, except for 2 things, error (beep) during install and it looks like the error was during Grunt JS build. Then, lets encrypt did not install. As noted in other previous tickets, the Grunt is in force mode, so it keeps trucking. Could someone please confirm if the below errors are indeed a problem? It would seem that I am missing some javascript and would like to know that, for sure, prior to using in event. Will this be an issue for me?

These issues seem to have been merged and fixed last aug, here is note on #555:
Merge #551, #555, #556, and #557 #559

Running "run:flow" (run) task
Launching Flow server for /var/www/fbctf/src
Spawned flow server (pid=22886)
Logs will go to /tmp/flow/zSvarzSwwwzSfbctfzSsrc.log
Monitor logs will go to /tmp/flow/zSvarzSwwwzSfbctfzSsrc.monitor_log
Started a new flow server: -Please wait. Server is starting up
Please wait. Server is initializing (starting up)
Please wait. Server is initializing (parsed files 0)
Please wait. Server is initializing (parsed files 0)
Please wait. Server is initializing (parsed files 717)
Please wait. Server is initializing (parsed files 717)
Please wait. Server is initializing (parsed files 717)
Please wait. Server is initializing (parsed files 717)
Please wait. Server is initializing (resolving dependencies)
Please wait. Server is initializing (calculating dependencies)
Please wait. Server is initializing (merged files 0/4 (0.0%))
Please wait. Server is initializing (finishing up)
Please wait. Server is handling a request (starting up)
Please wait. Server is handling a request (collating errors)
Error -------------------------------------------------------------------------------------- src/static/js/admin.js:5:24

Cannot resolve module dropkickjs.

5| var Dropkick = require('dropkickjs');
^^^^^^^^^^^^

Error -------------------------------------------------------------------------------------- src/static/js/admin.js:6:17

Cannot resolve module jquery.

6| var $ = require('jquery');
^^^^^^^^

Error -------------------------------------------------------------------------------------- src/static/js/clock.js:3:17

Cannot resolve module jquery.

3| var $ = require('jquery');
^^^^^^^^

Error ------------------------------------------------------------------------------------ src/static/js/fb-ctf.js:12:18

Cannot resolve module d3.

12| var d3 = require('d3');
^^^^

Error ------------------------------------------------------------------------------------ src/static/js/fb-ctf.js:13:17

Cannot resolve module jquery.

13| var $ = require('jquery');
^^^^^^^^

Error ------------------------------------------------------------------------------------ src/static/js/fb-ctf.js:14:23

Cannot resolve module keycode.

14| var Keycode = require('keycode');
^^^^^^^^^

Error ------------------------------------------------------------------------------------- src/static/js/filter.js:3:17

Cannot resolve module jquery.

3| var $ = require('jquery');
^^^^^^^^

Found 7 errors
Warning: non-zero exit code 2 Used --force, continuing.

Running "browserify:dist" (browserify) task

Bundle src/static/build/app-browserify.js created.

Running "copy:browserify" (copy) task
Copied 1 file

Running "sass:dist" (sass) task

Done, but with warnings.
[+] Installing nginx and certificates


all logs attached
errorlog.txt

It is also interesting that lets encrypt was not executed, and there are no errors as in previous comments on pull request here.

@v1ncenth
Copy link
Contributor

v1ncenth commented Aug 6, 2018

Those errors can be ignored. It should be working fine without issues.

@harperaa
Copy link
Author

harperaa commented Aug 6, 2018

Thanks. Should I start another issue with lets encrypt not executing during prod install, or is that normal?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants