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

Aberta
  • Algo errado?
#36,178 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
Meio dia
Facilidade para iniciantes
66/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
frontend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
TypeScript
Estrelas
24.8k
Forks
6.4k
Merge médio
59min
PRs com merge (30d)
418

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pingdotgg/t3code

Todas as issues de pingdotgg/t3code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.