You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zen.api.error.requestBlockedByUpstreamProvider was updated in en.ts by #41819 to tell users their account was blocked for ToS/fraud and to contact help@anoma.ly. All 17 non-English locales still carry the pre-#41819 meaning — a literal "request blocked by upstream provider" (zh: 请求被上游提供商阻止, ja: 上流プロバイダーによりリクエストがブロックされました, ko/de/fr/ru/ar similar).
Result: non-English users hitting an account block see what reads as an infrastructure outage, and never get the actual reason or the appeal contact. There are ~25 open issues quoting "Request blocked by upstream provider" — several from zh/ru speakers treating it as a service outage rather than an account action.
The locale files appear to be bulk-synced (periodic "sync" commits updating all locales together), so a hand edit to zh.ts alone probably gets overwritten. If the translation source is internal this may just need a re-sync of that key; if community edits to locale files are welcome, happy to PR corrected strings for the affected locales.
Steps to reproduce
Compare packages/console/app/src/i18n/en.ts (zen.api.error.requestBlockedByUpstreamProvider, changed in fix(console): update blocked account message #41819) against the same key in zh.ts, ja.ts, ko.ts, etc.
Or trigger the blocked-account path with a non-English Accept-Language — the response says "blocked by upstream provider" instead of the account-block notice.
Description
zen.api.error.requestBlockedByUpstreamProviderwas updated inen.tsby #41819 to tell users their account was blocked for ToS/fraud and to contact help@anoma.ly. All 17 non-English locales still carry the pre-#41819 meaning — a literal "request blocked by upstream provider" (zh: 请求被上游提供商阻止, ja: 上流プロバイダーによりリクエストがブロックされました, ko/de/fr/ru/ar similar).Result: non-English users hitting an account block see what reads as an infrastructure outage, and never get the actual reason or the appeal contact. There are ~25 open issues quoting "Request blocked by upstream provider" — several from zh/ru speakers treating it as a service outage rather than an account action.
The locale files appear to be bulk-synced (periodic "sync" commits updating all locales together), so a hand edit to zh.ts alone probably gets overwritten. If the translation source is internal this may just need a re-sync of that key; if community edits to locale files are welcome, happy to PR corrected strings for the affected locales.
Steps to reproduce
packages/console/app/src/i18n/en.ts(zen.api.error.requestBlockedByUpstreamProvider, changed in fix(console): update blocked account message #41819) against the same key inzh.ts,ja.ts,ko.ts, etc.Accept-Language— the response says "blocked by upstream provider" instead of the account-block notice.