GPT-6.1 Sol · Heavy

feature-localization-fallbacks-server-side-discourse-cursor

Discourse · Ruby · S · 30–99 lines · 6 files

The generalist plus 9 specialist lens agents in parallel, then the same verify and dedup steps. Judge: Claude Haiku 5.5.

Gold bugs found
1 of 2
Comments published
2
Comments matching a bug
1
Comments not matching
1
Cost of this PR
$0.968

Published comments (2)

mediumbugconfig/initializers/i18n.rb:17

Site-dependent fallbacks leak cached translations across sites — Ukrainian users can receive another site's cached fallback because the accelerator cache key omits `SiteSetting.default_locale`; check the accelerator's cache-key construction. Include the site default locale or complete fallback chain in that key.

mediumbugconfig/initializers/i18n.rb:4-5

Locale-specific pluralization breaks incomplete Ukrainian translation hashes — Ukrainian entries such as `too_many_mentions` and `too_many_mentions_newuser` have only `one` and `other`, so counts selecting `few` or `many` raise `I18n::InvalidPluralizationData`. Add the required categories to those translation hashes before enabling `I18n::Backend::Pluralization` globally.

Gold bugs found (1)

mediumThe translation cache key does not include the site or its default locale, but fallback results now depend on SiteSetting.default_locale, so multisite processes or a changed default locale serve stale fallback translations.

Gold bugs missed (1)

mediumFallback locale catalogs are only loaded in the controller's set_locale filter, while translate loads just the current locale, so translations outside requests (jobs, mailers) cannot fall back to the site default or English.