Screenshot
[drag & drop image(s) here!]
Description
This is buggy frontend pagination logic, since i updated to a fresher version of superset this happened. Launched superset from docker-compose.yml and set a production environment. Take any table and try to turn on the server pagination, so you can replicate the same problem [describe the issue here!]
Design input
[describe any input/collaboration you'd like from designers, and
tag accordingly. For design review, add the
label design:review. If this includes a design proposal,
include the label design:suggest]
Comment From: dosubot[bot]
Hi @aizeld! I'm Dosu and I’m helping the superset team.
This looks like a known issue with server-side pagination in table visualizations—there have been recent reports where changing row limits or enabling server pagination causes the frontend table to not update correctly, even though the backend query and pagination controls reflect the right values. This is likely due to state synchronization problems between the frontend controls and the backend query logic, especially after recent updates to the table chart components and pagination controls [example issue].
Server pagination is implemented as an experimental feature and relies on the correct state being passed through several frontend components (control panel, TableChart, DataTable). Recent pull requests have changed how sorting and pagination controls work, which may have introduced regressions or subtle bugs [PR #33540].
A few things to check or try: - Make sure "Server pagination" is enabled in the chart controls and that "Server Page Length" is set to your desired value. - If the table doesn't update when you change the page or row limit, try toggling server pagination off and on, or refreshing the chart. - If you see a mismatch between the pagination controls and the data shown, it may be a state sync issue—this has been reported in recent versions and is under discussion [related issue].
If you can share the exact Superset version and describe the buggy behavior in more detail (e.g., what happens when you change pages or row limits), I can help pinpoint whether it's a regression from a specific update or a configuration issue.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: LisaHusband
@aizeld which chart? Maybe I can fix it 😄
Comment From: aizeld
@LisaHusband it's table chart. Should i rebuild frontend just for test?
Comment From: LisaHusband
if you use docker from this project, No. if not ,maybe.
Comment From: aizeld
@LisaHusband can you replicate this problem on your machine? how can i fix it?
Comment From: LisaHusband
@aizeld Я только что загрузил последнюю версию исходного кода и использовал встроенный в проект набор данных. При работе с таблицей и пагинацией отображение было нормальным, никаких проблем не возникло. Возможно, вам стоит проверить, есть ли в вашем наборе данных достаточно записей для отображения одной страницы с указанным размером. Либо вы можете сделать скриншот с более подробными параметрами настройки. Также вы можете создать пример набора данных (если есть чувствительные данные — используйте фиктивные данные для моделирования
