Model-server banner's restart hint is untranslated in Arabic
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend, internationalization
Research direction
Start in ConnectionBanner.tsx, where the two restart and start-by-hand hints are hard-coded in English beside the translated banner.serverHung and banner.serverStopped strings. Add en and ar translation keys for both hints, and keep the command inside a code element with dir="ltr". Done when the Arabic banner shows no English hint text and the file's hardcodedText baseline is lowered to match.
Written by the indexing model from the issue text.
Description
The model-server banner's start/restart hint is still English in the Arabic UI, so an Arabic user sees an English phrase in the middle of an Arabic warning.
🔍 Technical details
ConnectionBanner.tsxhard-codes'If it stays this way, restart it: 'and'To start it by hand, run 'next to the translatedbanner.serverHung/banner.serverStoppedtext.- Fix: add en + ar keys for both hints and keep the
<code>commanddir="ltr"; lower thehardcodedTextbaseline for the file. - Raised in review of #8019, where it predates the change.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 169
- Avg merge
- 12h 19m
- Merged PRs (30d)
- 777
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from amd/gaia
-
bug needs-human p2
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug cli p2
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
agent-ui bug needs-human p3
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug cli needs-human p3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
agent-ui bug p3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
Similar issues
-
Unknown stop ID in slow zone data crashes post formatting and skips the rest of that day's postsOpenbackend bug tm-new-volunteer
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
transitmatters/mbta-slow-zone-bot#81 · 1 comment ·
-
area:schema documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
risk:high type:ci
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
spacetelescope/rdmt-spire#49 ·
Maintainers usually reply within 1 day