pingdotgg / pingdotgg/t3code

[Bug]: Command, skill, model and file search finds nothing when the query is typed on a non-Latin keyboard layout

Open
#11,723 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Switch the operating system input source to a non-Latin layout that is positionally based on US QWERTY. Russian, Ukrainian, Belarusian, Bulgarian, Serbian, Macedonian, Kazakh, Greek, Hebrew, Armenian, Georgian, Arabic, Persian and Thai layouts all qualify.
  2. In the composer, type / and then press the keys that spell an existing command, for example the keys of model.
  3. Repeat with $ and a skill name, with @ and a file name, with the Cmd+K command palette, and with the Settings search field.
Expected behavior

The menu finds the command, skill, model, file or setting. The keys pressed are the ones that spell its name on a US layout, and the names being searched are always Latin, so the intent is unambiguous.

Actual behavior

Every one of those surfaces shows an empty result. The composer menu reads "No matching command.", the palette and Settings search return nothing, and @ returns no files.

Nothing matches because the keystrokes produce the letters of the active layout while command names, skill names, model ids and file paths are Latin. The user has to notice the mismatch, switch input source, and retype. This affects every client surface and every one of the layouts above.

Impact

Minor bug or occasional failure

Version or commit

main at 01e05c152

Environment

Reproduced on macOS. The matching happens in shared client code and on the server's path search, so the behavior is the same on web, desktop and mobile, and independent of the operating system.

Additional context

I have a fix and will open a pull request referencing this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the shared client matching used by the composer, Cmd+K palette, Settings search, and @ file search, then inspect the server path search mentioned in the report. Reproduce with a positional non-Latin layout and verify that keys spelling Latin names on a US layout return commands, skills, models, files, and settings across the listed surfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, frontend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.