Too much whitespace between columns in event picker
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start by locating the event picker and its table or column-width rendering code, then inspect how widths and suppressed fields are handled on narrow screens. Done means the excessive gaps, especially around TOKENS, are reduced while the visible fields remain readable and useful at low screen widths.
Written by the indexing model from the issue text.
Description
The event picker looks like this:
agentop · do I have assigned PRs in this repo? (11007a7ad3d9c1c2e3dc997472fcec5c) · agent=bob-shell
LAST 1H — · TODAY — · 7 DAYS — · THIS MONTH —
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
# TIME DIR PHASE ACTION PLUGIN METHOD STATUS DURATION TOKENS COST HOST
1 10:26:05.71 out req — — api.us-east.bob.ibm…
1 10:26:06.15 out resp — — 200 435ms api.us-east.bob.ibm…
2 10:26:06.15 out req — — api.us-east.bob.ibm…
2 10:26:06.21 out resp — — 200 53ms api.us-east.bob.ibm…
3 10:26:06.27 out req — — api.us-east.bob.ibm…
3 10:26:06.34 out resp — — 200 70ms api.us-east.bob.ibm…
4 10:26:06.77 out req tunnel — s3.us-south.cloud-o…
5 10:26:28.51 out req observe inference-parser openai/gpt-oss-20b 1,364 api.us-east.bob.ibm…
6 10:26:28.51 out req observe inference-parser router api.us-east.bob.ibm…
6 10:26:28.57 out resp observe inference-parser router 200 56ms api.us-east.bob.ibm…
7 10:26:28.64 out req observe inference-parser premium-ide 10,593 api.us-east.bob.ibm…
5 10:26:29.05 out resp observe inference-parser openai/gpt-oss-20b 200 542ms 158 api.us-east.bob.ibm…
7 10:26:30.60 out resp observe inference-parser premium-ide 200 1.96s 102 api.us-east.bob.ibm…
There is a LOT of space between columns, especially the "TOKENS" column.
We are low on screen width, and it is confusing for users when fields get suppressed do to screen width but there looks like a lot of visible space for the column.
- Dominant language
- Go
- Stars
- 13
- Forks
- 40
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 204
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/cortex
-
feedback laptop
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
Similar issues
-
cvss-severity:high devguard l3montree-cybersecurity/devguard/devguard pkg:golang/github.com/l3montree-dev/devguard risk:low state:open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
l3montree-dev/devguard#3146 · 1 comment ·
Maintainers usually reply within 1 day
-
CLI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
databricks/cli#6910 ·
Maintainers usually reply within 1 day
-
Table presenter appends a spurious ", ..." to the FIX column when all fix versions are already shownOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
canonical/microceph#900 · 1 comment ·
Maintainers usually reply within 1 day
-
vulncheck or vulndb
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day