Too many run group cards per run group result page #36

New Issue

bstein · 2026-07-11T06:26:09Z

bstein commented

2026-07-11 06:26:09 +00:00

What happened

There was a 4th row of run group cards appearing on the first paginated results set.

What should have happened

Run Group cards should all be of the same fixed size and there should be a maximum of 3 rows and 4 columns per paginated result set.

Context

Page URL: https://veles.bstein.dev/runs
Route: runs
Path: /runs
Backend version: 0.6.22
Frontend version: 0.6.22
Sim version: 0.6.22

## What happened There was a 4th row of run group cards appearing on the first paginated results set. <img width="1440" alt="image.png" src="attachments/49621627-858c-4579-ab9d-0135b1f50329"> ## What should have happened Run Group cards should all be of the same fixed size and there should be a maximum of 3 rows and 4 columns per paginated result set. ## Category - kind: ui-table - severity: obvious ## Context - Page URL: https://veles.bstein.dev/runs - Route: runs - Path: /runs - Backend version: 0.6.22 - Frontend version: 0.6.22 - Sim version: 0.6.22

image.png

524 KiB

bstein added the

kind/ui

severity/obvious

labels 2026-07-11 06:26:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#36