fix(i18n): publish the translation bundle only once it is complete

InitLocalizer filled the shared bundle in place, and the Telegram bot
runs it again while the panel is serving, so a request could read the
bundle's maps while they were being written and the process died on a
concurrent map access. Build the bundle privately and publish it, and
the bot and web localizers, through atomic pointers; the lazy load in
the middleware publishes only if nothing else did first.
This commit is contained in:
MHSanaei
2026-10-31 09:11:54 +00:00
parent e3736564a3
commit f1e1b0fb0c
7 changed files with 89 additions and 32 deletions
+2 -3
View File
@@ -636,9 +636,8 @@ func localizeWithRealBundle(t *testing.T) {
if _, err := bundle.ParseMessageFileBytes(data, path); err != nil {
t.Fatalf("parse %s: %v", path, err)
}
orig := locale.LocalizerBot
locale.LocalizerBot = i18n.NewLocalizer(bundle, "en-US")
t.Cleanup(func() { locale.LocalizerBot = orig })
orig := locale.SwapBotLocalizer(i18n.NewLocalizer(bundle, "en-US"))
t.Cleanup(func() { locale.SwapBotLocalizer(orig) })
}
// seeding a client bound to a Telegram user, which the client screens key on