build-pypi gets stuck at building "templates"

[cweickhmann]

There is an issue I am experiencing at least with the OpenSlides/OpenSlides commit hashes OpenSlides/OpenSlides@123b7c7 and OpenSlides/OpenSlides@d2c4aff.

This happens with openslides-docker commits 4d15c56 and 81d300e.

The installation (following the instructions in buildpypi/README.md) gets stuck at the end of the installation log below, after building (?) "templates":

...
ckeditor#4.7.3 bower_components/ckeditor
[12:09:19] Using gulpfile /app/openslides/gulpfile.js
[12:09:19] Starting 'default'...
[12:09:19] Starting 'js'...
[12:09:19] Starting 'js_libs'...
[12:09:19] Starting 'pdf_worker'...
[12:09:19] Starting 'pdf_worker_libs'...
[12:09:19] Starting 'templates'...
[12:09:19] Starting 'css_site'...
[12:09:19] Starting 'css_projector'...
[12:09:19] Starting 'css_libs'...
[12:09:19] Starting 'fonts_libs'...
[12:09:19] Starting 'angular_chosen_img'...
[12:09:19] Starting 'ckeditor'...
[12:09:19] Starting 'translations'...
[12:09:19] Starting 'ckeditor_defaults'...
[12:09:19] Starting 'ckeditor_skins'...
[12:09:19] Starting 'ckeditor_plugins'...
[12:09:19] Starting 'ckeditor_lang'...
[12:09:19] Finished 'pdf_worker' after 745 ms
[12:09:19] Finished 'ckeditor_defaults' after 602 ms
[12:09:19] Finished 'angular_chosen_img' after 753 ms
[12:09:20] Finished 'css_projector' after 759 ms
[12:09:20] Finished 'css_site' after 839 ms
[12:09:20] Finished 'ckeditor_lang' after 842 ms
[12:09:20] Finished 'css_libs' after 1.09 s
[12:09:20] Finished 'fonts_libs' after 1.22 s
[12:09:20] Finished 'pdf_worker_libs' after 1.31 s
[12:09:20] Finished 'translations' after 1.35 s
[12:09:20] Finished 'ckeditor_skins' after 1.21 s
[12:09:21] Finished 'js' after 1.83 s
[12:09:21] Finished 'templates' after 2.07 s
[12:09:23] Finished 'js_libs' after 3.87 s
[12:09:23] Finished 'ckeditor_plugins' after 4.51 s
[12:09:23] Finished 'ckeditor' after 4.67 s
[12:09:23] Finished 'default' after 4.68 s
Done in 113.53s.
[12:09:29] Using gulpfile /app/openslides/gulpfile.js
[12:09:29] Starting 'default'...
[12:09:29] Starting 'js'...
[12:09:29] Starting 'js_libs'...
[12:09:29] Starting 'pdf_worker'...
[12:09:29] Starting 'pdf_worker_libs'...
[12:09:29] Starting 'templates'...
[12:09:29] Starting 'css_site'...
[12:09:29] Starting 'css_projector'...
[12:09:29] Starting 'css_libs'...
[12:09:29] Starting 'fonts_libs'...
[12:09:29] Starting 'angular_chosen_img'...
[12:09:29] Starting 'ckeditor'...
[12:09:29] Starting 'translations'...
[12:09:29] Starting 'ckeditor_defaults'...
[12:09:29] Starting 'ckeditor_skins'...
[12:09:29] Starting 'ckeditor_plugins'...
[12:09:29] Starting 'ckeditor_lang'...
[12:09:31] Finished 'pdf_worker' after 2.18 s
[12:09:31] Finished 'css_projector' after 2.19 s
[12:09:31] Finished 'css_site' after 2.2 s
[12:09:31] Finished 'angular_chosen_img' after 2.2 s
[12:09:31] Finished 'ckeditor_defaults' after 1.83 s
[12:09:31] Finished 'ckeditor_lang' after 2.09 s
[12:09:35] Finished 'css_libs' after 6.7 s
[12:09:36] Finished 'fonts_libs' after 6.86 s
WARN: Output exceeds 32000 characters
WARN: Output exceeds 32000 characters
[12:09:57] Finished 'pdf_worker_libs' after 28 s
[12:09:57] Finished 'translations' after 28 s
[12:09:57] Finished 'ckeditor_skins' after 28 s
[12:09:57] Finished 'js' after 29 s
WARN: Output exceeds 32000 characters
[12:09:58] Finished 'templates' after 29 s

Any idea what might be wrong?

[jsaalfeld]

I build the pypi files according to the OpenSlides 3.0 details, but it should work with prior versions as well.

I ran the build with the above mentioned commits and it resulted in a working pypi file.

docker run --env NEWUID=$(id -u) \
  --env REPOSITORY_URL=https://github.com/OpenSlides/OpenSlides.git \
  --env BRANCH=master \
  --env COMMIT_HASH=d2c4aff7a4e3d27e2ac8f2ce55c446cabe032f33 \
  -v $(pwd)/build:/app/build \
  -it os-buildpypi

The command ran after the build successfully an pypi *.tar.gz in the build folder which can be used down the road. Can you post a paste of your complete console with all the commands you used?

[FinnStutzenstein]

Hi, I had problems with gulp on weaker machines before. I can't really remember, but if you watch gulp with a process monitor, it might allocate too much memory. I think, that I crashed a resource limited Zen-instance with this command. Sorry that I do not remeber it cleary, it was a while ago.

Can you give some specs about your machine?

[cweickhmann]

Thank you for your feedback. I had the revelation this morning: Gulp just needs lots of RAM which the VM I ran it on did not have: 1 GB is not enough, 4 GB does the job.

I would suggest a warning in the docs, though.