Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[4.5.0rc0] Clientside callback runs with a stale Input value after set_props on page load (regression from 4.4.1, clientside callbacks now exempt from the HTTP-slot budget)

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

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python, react, typescript
Domínio
frontend, testing-qa, web-dev

Direção de pesquisa

Start in observers/prioritizedCallbacks.ts and observers/requestSlot.ts, then compare the built dash_renderer.min.js behavior with and without clientside callbacks counting toward the HTTP-slot budget. Reproduce the full-app sequence using the readUrl and tabSearch callbacks, and trace the callback scheduling and Input values. Done means the page settles after load and preserves ?tab=history without the infinite loop.

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

Descrição

Describe the bug

On a page with many server callbacks firing at load, a URL-to-component sync set up with two clientside callbacks goes into an infinite loop on 4.5.0rc0. It works on 4.4.1.

  • readUrl: Input url.search, prevent_initial_call="initial_duplicate". It calls dash_clientside.set_props("tabs", {"value": <tab from ?tab=>}).
  • tabSearch: Input tabs.value, State url.search, Output url.search (allow_duplicate=True), prevent_initial_call=True. It writes ?tab=<value> back to the URL.

Loading /page?plan=21&tab=history on 4.5.0rc0 gives this trace (store = the tabs.value in window.store):

1397ms  store tabs.value undefined -> "scope"   (layout default)
1748ms  readUrl: set_props("tabs", {value: "history"}) ; store -> "history"
1759ms  tabSearch runs, triggered [{"prop_id":"tabs.value","value":"scope"}]   <-- stale value
1934ms  tabSearch runs, triggered [{"prop_id":"tabs.value","value":"history"}]
...     the stale run writes ?plan=21, readUrl sets the tab back to "scope", tabSearch gets "history"... forever

tabSearch runs twice, and the first run gets the layout's stale value even though the store already holds the value set_props wrote. On 4.4.1 it runs once, with "history".

Bisected to the renderer change in observers/prioritizedCallbacks.ts / observers/requestSlot.ts (from #3931, commit ce7530ca25), which exempts clientside callbacks from the 12-slot HTTP budget. With only !cb.callback.clientside_function && removed from usesRequestSlot in the built dash_renderer.min.js, so clientside callbacks count toward the budget again as in 4.4.1, the same page settles: one request after load, ?tab=history kept, History tab selected. With the stock 4.5.0rc0 renderer the page loops until the browser tab crashes.

The CHANGELOG entry for #3931 doesn't mention the scheduling change.

Repro status

Our reduced app (dmc.Tabs + the two callbacks above, a router callback returning the page, 20 slow server callbacks on load) did NOT reproduce the 4.4.1/4.5 difference, so the exact extra condition is still unknown. The evidence above comes from the full app, where swapping only that renderer line toggles the bug. Happy to test a candidate fix.

Environment: dash 4.5.0rc0 (FastAPI backend), dash-mantine-components 2.8.0, React 18.3.1 (default), Chrome stable (Playwright), Python 3.14.

Workaround: guard the URL writer against its own echo (ignore tabs.value events until the value set_props wrote comes back).

Linguagem predominante
Python
Estrelas
24.4k
Forks
2.3k
Merge médio
2d 23min
PRs com merge (30d)
17

Preparar o ambiente

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 plotly/dash

Todas as issues de plotly/dash

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

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