Skip to content

phsl / new-api

Go to a project
Switch branch/tag
  1. 05 Jun, 2026 7 commits
  3. 04 Jun, 2026 2 commits
  5. 03 Jun, 2026 4 commits
  7. 02 Jun, 2026 5 commits
  9. 01 Jun, 2026 6 commits
  11. 31 May, 2026 2 commits
  13. 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
  15. 29 May, 2026 2 commits
  17. 28 May, 2026 3 commits
  19. 27 May, 2026 1 commit
  21. 26 May, 2026 6 commits
    • fix: keep token log filters exact · 74985fa8
      CaIon committed
    • fix: keep usage log filters exact unless wildcard is explicit (#5097) · 1d320373
      yyhhyyyyyy committed
    • fix(web): improve channel and usage log UI · dc245ae7 
      Fixes #5121
      CaIon committed
    • feat(theme): add simple-large preset, xl scale and clean up channel badge dots · f8add4ca 
      Implement the Simple Large-font theme preset and xl font scale options to enhance interface accessibility. Remove status indicator dots from channel badges in logs to keep the table layout visual and clean.
      CaIon committed
    • 🐛 fix(system-settings): resolve save detection and number input NaN issues · 65f8afe9 
      System settings forms that used flat dotted API keys (e.g.
`performance_setting.monitor_cpu_threshold`) with React Hook Form were
broken: RHF stores dotted paths as nested objects on update, while dirty
checks and submit comparisons still read flat keys from defaults. Users
could edit values but always saw "No changes to save".

Refactor affected sections to use nested Zod schemas and default values
for RHF, with explicit helpers to convert between nested form state and
flat API keys. Track a normalized baseline in refs for accurate change
detection and post-save resets.

Add `safeNumberFieldProps` to prevent native `<input type="number">`
from writing NaN into form state when cleared. NaN caused Zod validation
to fail silently and made the save button appear unresponsive. The
helper ignores non-finite updates so controlled inputs snap back to the
last valid value, matching legacy Semi InputNumber behavior.

Sections refactored for dotted-key handling:
- maintenance/performance-section
- models/grok-settings-card
- auth/passkey-section
- auth/oauth-section
- auth/section-registry (pass attachment_preference raw; normalize in section)

Sections migrated to safeNumberFieldProps:
- maintenance/performance-section
- models/grok-settings-card
- integrations/monitoring-settings-section
- integrations/payment-settings-section
- integrations/creem-product-dialog
- general/pricing-section (USD exchange rate)
- general/system-behavior-section
- content/dashboard-section

Optional numeric fields (e.g. custom currency exchange rate) keep their
existing empty-to-undefined semantics and are intentionally unchanged.
      t0ng7u committed
    • 🎨 fix(logs): tune usage table typography · 5bc4c748 
      Set usage log tables to a balanced 13px default and keep log badges aligned with the active theme font.
      CaIon committed