Closed Gauntlet173 closed 2 years ago
Rolling back three versions still doesn't solve the problem, which is strange. Have tried re-ordering the loading of the langauge files, to no effect.
Someone seems to report a fix that requires using a combination of 8.0.2 but with the 8.0.4 version of the msg files from GitHub.
That's the best lead I have, currently. Otherwise we're just waiting for a patch.
Unbelievably, using the 8.0.4 version of en.js with the 8.0.2 version of blockly, and loading the script for the custom version of en.js immediately after blockly_compressed.js seems to work. That has been done in blawx and test editors, and should work going forward. Going to add an issue to remove these adjustments once the patch is released that solves the problem.
This is a problem that has been discussed as an open issue with Blockly. They are working on changes that would solve this problem in the most recent beta version of Blockly.
To use the beta version of blockly, check out the active versions of blockly at npm. Find the relevant npm package, and use
in the Dockerfile somewhere after
ADD . blawx
, and comment out thegit clone
line for blockly.I don't think it makes sense to switch to the npm install process generally, because it seems to be installing an enormous amount of cruft that is for development purposes only.
What we are going to have to do is monitor the above issue, and the Blockly releases, and see when this gets fixed.
Going to see if there is a previous version of blockly that doesn't have this problem, that we can use until this issue is resolved.