You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Sentry and PostHog schedule lists clip task identifiers and cannot reflow in REPL #6699
Follow-up to the CLI/REPL audit in #6693 and #6696.
Affected paths:
/sentry digest schedule list
/sentry uptime watch list
/posthog report schedule list
Their Click handlers render eight-column rich.Table grids (ID, cron, TZ, provider, chat, project/period, enabled, last run). The REPL captures ANSI output, applies a replay gutter and generic output preview, and cannot reflow that grid after resizing. At 40 columns, key fields including task IDs are squeezed/clipped. Unlike /cron list after #6695, these lists do not retain native responsive record renderables.
Use one shared record renderer for these task-kind lists across CLI and REPL, keep full task IDs/timezones/destination/project or period information, preserve empty-state wording and kind filters, and reserve stdin for the exact nested list paths. Other invocations should keep existing CLI delegation. Validate mixed task kinds and 40/100/160 column output, literal markup, no generic collapse, native transcript replay, and the next editable prompt. Follow CI and Greptile/Codex review through completion.
I noticed #6700 addressed it and was closed on Oct 14 without merging. Is a replacement already in progress, or is this free to take? If it's free, I'd reuse the shared record renderer from #6695/#6730 for the Sentry and PostHog schedule lists.
I’m taking this as a replacement for #6700. I’ll reuse the shared responsive record renderer so the Sentry and PostHog schedule lists retain full task IDs and reflow in the REPL, with focused regression coverage.
Activity
snehitsharma commentedon Oct 16, 2026
I noticed #6700 addressed it and was closed on Oct 14 without merging. Is a replacement already in progress, or is this free to take? If it's free, I'd reuse the shared record renderer from #6695/#6730 for the Sentry and PostHog schedule lists.
shrayjaiswal050-design commentedon Oct 17, 2026
I’m taking this as a replacement for #6700. I’ll reuse the shared responsive record renderer so the Sentry and PostHog schedule lists retain full task IDs and reflow in the REPL, with focused regression coverage.