Potential problem on stable branch on ARM

MattDHarding

So I had the develop branch working all ok and fixed a bug there.
When I tried to switch to the stable branch I ran into trouble.

Trying to run the i18l-compile gives this error that looks like it's trying to run a non-arm exe

docker-compose -f dev.yml run --rm front yarn run i18n-compile
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
WARNING: The DJANGO_ALLOWED_HOSTS variable is not set. Defaulting to a blank string.
yarn run v1.22.17
$ scripts/i18n-compile.sh
++ dirname scripts/i18n-compile.sh
+ cd scripts/..
+ source scripts/utils.sh
++ tail -n +2 src/locales.js
++ jq '.locales[].code'
++ sed -e 's/export default //'
++ grep -v en_US
++ xargs echo
scripts/i18n-compile.sh: line 6: /usr/local/bin/jq: cannot execute binary file: Exec format error
+ locales=
+ mkdir -p src/translations
Done in 0.26s.

When I get to the front end it looks like this:
[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2022-02-12/1644654686-34477-image.png]

Here is what my Chrome browser console shows:
https://www.toptal.com/developers/hastebin/uvematesaj.sql

MattDHarding

Just to clarify, this is running the development environment.

Also, I get the same error with i18n-compile when on the develop branch too, but the develop branch ultimately works just fine for me.

egon0

Interesting.

https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/front/Dockerfile#L4

This docker file is only used in develop context and is not multiarch ready. We explicitly download the linux64 binary of the jq utility. We need to install it via the package manager of the node image and not via curl from GitHub to fix this.

MattDHarding

Yea that certainly looks to be the problem with that error message, sadly I don't think that relates to me not being able to run the stable branch as I get that error on stable and develop.

gcrk

MattDHarding Its the same for develop and stable, but this image is not shipped for production. Would you mind to create an issue so I can have a look as soon as I can get back to it?

gcrk

Nevermind, I don't need an issue. I am about to push a fix for it to develop, if this works (please test, @MattDHarding ), I will backport this to stable, too.

MattDHarding

gcrk that certainly cleared up the issue with compiling the languages thanks!, but sadly that was a red herring in my original issue.

gcrk

MattDHarding I am on it, I kind of experience the same issue currently. Sadly your paste is gone, can you post the message again? In the best case just here at the forum so it stays 🙂

gcrk

@MattDHarding Can you just set a theme in the footer?

MattDHarding

So selecting a theme was hard due to the way that the page was rendering, but once I managed to change the theme my problem went away. I can't actually get it to happen again now, stopped the docker, closed my browser, cleared out cookies...

Of course I went and tried the above before I took a copy of the console window!

gcrk

MattDHarding I don't think we need the logs anymore, its interesting this happens sometimes, but only in firefox. I'll keep an eye on it 🙂 Glad its working now!

MattDHarding

gcrk I'll let you know if it comes back, it happened in Chromium for me.