assets: truncation at random (?) point

[jacquerie]

http://inspire-nightly.cern.ch/ currently looks pretty bad:

This is due to the infamous truncation bug we've been intermittently seeing on our development machines. It could be related to this other truncation bug: miracle2k/webassets#468. The only issue with this theory is that the file currently served is 51288 bytes, but this could be the effect of the clean_css filter run afterwards.

• Remove the clean_css filter and confirm that the truncation happens at 65536 bytes.
• Work around the issue by pinning the known functioning version of node-sass when installing.

[jacquerie]

this could be the effect of the clean_css filter run afterwards

This is actually the case: the file currently served after removing the clean_css filter is exactly 65536 bytes.

[zzacharo]

@jacquerie If this is the same problem that i dealt with when i installed inspirehep, i just ran npm install node-sass@3.4.2.

[jmartinm]

@zzacharo for the moment it would be enough if you can update the documentation to specify the node-sass version needed.

[jacquerie]

it would be enough if you can update the documentation to specify the node-sass version needed.

Sadly not :(

The fact is, docker-compose -f docker-compose.deps.yml run --rm assets will install things inside of the web container, which will fetch its own version of node-sass (currently 3.10.1). If we try to add node-sass@3.4.2 to the css bundle in inspirehep/modules/theme/bundles.py then we get an ELIFECYCLE error: sass/node-sass#1687 (comment)

[jacquerie]

This is also blocking #1607.