Weird encoding issue on categories page

[hendersj]

@supermathie

You can easily check with:

○ → ipython3

In [1]: 'Esta sección del Foro se dedica a las personas usuarias de openSUSE que forman parte de la comunidad lingüística castellana
   ...: , de tal forma que dichas personas puedan consultar y participar en el foro en dicha lengua (sea el dialecto español o cualq
   ...: uiera de las variedades latinoamericanas, etc.).'.encode('utf-8').decode('iso-8859-1')
Out[1]: 'Esta sección del Foro se dedica a las personas usuarias de openSUSE que form

Cool, thanks for that.

@pfaffman

My guess is that something is doing some kind of caching. That’s not much help, but that’s what I’d try to look for.

I thought that might be the case, but changing the message resulted in an update, so I don’t think it’s caching - it’s something encoding incorrectly.

@pfaffman

Unless they just hate Docker, they can build their own images with discourse_docker. Then they can see exactly what is happening and not have to trust anyone else’s images.

I suggested a few options, but in the end, the infra team opted to just go with packages built using the build service. I don’t think it’s a “we hate docker” thing (though podman would probably be more likely what they’d want to use), but more a way of using the configuration management tools they’re using to manage everything in the same manner. Having a one-off that uses Docker/podman would add other complexities to using the CI/CD setup they’re using (or so I understand).

So ultimately, I set up my two sandboxes to be able to determine where issues are rooted so I could report them to the proper place; unfortunately, that means that when it is something in how we’ve built things, I have to chase down what we’re doing different from a standard Docker-based installation so we can fix it.