Skip to content

phsl / new-api

Go to a project
Switch branch/tag
  1. 06 Jun, 2026 2 commits
    • perf(web): improve dialog sizing and footer layout · 2eaa943d 
      - migrate frontend dialogs to the shared footer API so actions stay separated from scrollable body content.
- tune dialog dimensions for model analytics, prefill groups, billing history, channel model sync, and related workflows.
- update channel terminology and dialog action translations across supported locales.
      QuentinHsu committed
    • feat(web): add shared dialog wrapper · 7a5348ca 
      - introduce a reusable dialog component for consistent header, body, and footer layout.
- support per-dialog sizing, trigger rendering, initial focus, and close button controls.
- preserve base dialog open and close motion classes while allowing content-specific styling.
      QuentinHsu committed
  3. 05 Jun, 2026 8 commits
  5. 04 Jun, 2026 3 commits
  7. 03 Jun, 2026 4 commits
  9. 02 Jun, 2026 5 commits
  11. 01 Jun, 2026 6 commits
  13. 31 May, 2026 2 commits
  15. 30 May, 2026 2 commits
    • perf: order admin logs by created_at to use composite index (#5116) · 230a3592
      skynono committed
    • fix(model): correct idx_created_at_id index column order to (created_at, id) (#5191) · afb470e4 
      The idx_created_at_id composite index on the logs table was defined as
(id, created_at) because the GORM `priority` values on Id and CreatedAt were
swapped. Since `id` is the auto-increment primary key, a secondary composite
index leading with `id` is redundant with the PK and cannot accelerate
`created_at` range scans (a range column must sit at the index prefix).

This defeats the common log-listing queries
(`WHERE created_at BETWEEN ? AND ? ORDER BY id DESC LIMIT n` in
GetAllLogs/GetUserLogs) that the index name implies it should serve — the
optimizer falls back to scanning the primary key, degrading to near full-table
scans on large logs tables.

Swap the priorities so the column order becomes (created_at, id), matching the
index name and its intended purpose. idx_user_id_id and idx_created_at_type are
unaffected.

Note: GORM AutoMigrate does not change the column order of an already-existing
index with the same name, so existing deployments must rebuild the index
manually (see PR description for per-database DDL).

Co-authored-by: wuyupeng <wuyupeng@floatmiracle.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
      YuPeng Wu committed
  17. 29 May, 2026 2 commits
  19. 28 May, 2026 3 commits
  21. 27 May, 2026 1 commit
  23. 26 May, 2026 2 commits