[Bug]: Usage → Limits: accounts swap places on refresh, and ↻ +% counts only one of the accounts that reset together

Abierto
  • ¿Algo no está bien?
#36,178 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
66/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

Start in collectLimitPools and its orderReset sort in packages/shared/src/usageLimits.ts, then find where the ↻ +% total calls pool.resets.find(...). Check how the Usage → Limits page consumes that ordering. Done means account order stays fixed across refreshes when reset times are nearly equal, and the +% total includes every account resetting at the same moment, verified with two accounts resetting within seconds of each other.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

packages/contracts or packages/shared

Steps to reproduce
  1. sign in two Claude accounts whose 5-hour windows reset within a few seconds of each other (one of them with its weekly limit spent)
  2. open Usage → Limits and leave it open, or switch the environment filter
Expected behavior

account order stays put while the page is open, and the ↻ +% under the total adds up every account that resets at that moment

Actual behavior

accounts are sorted by next reset (orderReset in collectLimitPools, packages/shared/src/usageLimits.ts) so near-equal reset times swap on every refresh, and an account jumps to the end right after its window resets, so the row moves while i read it

↻ +% uses pool.resets.find(...) so with Claude 1 at 81% left and Claude 2 at 0%, both resetting in 3h 58m, it shows +6% or +50% depending on which one sorts first, instead of about +40%

Impact

Minor bug or occasional failure

Version or commit

0.1.10-nightly.20261113.4630

Environment

macOS desktop app, two environments

Logs or stack traces
Screenshots, recordings, or supporting files

No response

Workaround

No response

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
59 min
PR fusionados (30 d)
418

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.