This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-26
Channels
- # announcements (17)
- # babashka (68)
- # beginners (8)
- # biff (14)
- # calva (25)
- # cherry (10)
- # clj-kondo (1)
- # clj-on-windows (12)
- # cljsrn (6)
- # clojure (134)
- # clojure-berlin (1)
- # clojure-europe (33)
- # clojure-nl (4)
- # clojure-norway (6)
- # clojure-uk (10)
- # clojurescript (9)
- # datalevin (8)
- # datomic (34)
- # docker (1)
- # emacs (31)
- # fulcro (6)
- # honeysql (8)
- # java (7)
- # joyride (14)
- # kaocha (7)
- # malli (11)
- # nbb (4)
- # off-topic (11)
- # pedestal (14)
- # rdf (53)
- # re-frame (6)
- # reagent (39)
- # reitit (2)
- # releases (9)
- # rewrite-clj (14)
- # shadow-cljs (97)
- # specter (1)
- # testing (5)
- # tools-deps (12)
- # vim (4)
- # xtdb (9)
another possible debugging breadcrumb, around a UTF-8 encoding issue:
• I used to use clojure:latest
which seems to be Ubuntu-22.04
• above I see that we're thinking it's better to switch to the Debian images, so I tried out clojure:temurin-17-tools-deps-1.11.1.1165-bullseye
(Debian 11)
• I test-deployed a deps.edn app using next-jdbc to connect to a Postgres 14 cluster.
• I noticed my frontend browser UI was now showing eg. "Window Wall System ��� Full Height Spandrel"
where it used to show "Window Wall System – Full Height Spandrel"
• I chased through from the database: the db encoding was correct with a direct psql
query.
• if I went into the docker container and started a REPL, I could see that the string shown at the REPL was wrong.
• I played a bit of a hunch on what had changed, and it was the docker image.
• Hypothesis: the docker images vary in a bunch of their base env vars. The debian one is missing eg. LC_ALL
, LANG
, LANGUAGE
• going back to the ubuntu image made the issue go away
Anyone who understands more than I do about UTF-8 and Linux (which is practically nothing) know if this hypothesis seems reasonable? If so, I can work around it by just setting the env vars in my image.