Feature request: posthog-live - option to keep live events sorted by timestamp
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- cli
Research direction
Find the implementation and tests for posthog-live, then trace how incoming events are added to the displayed list. The request is for an optional timestamp-based ordering for development sessions with few events; done means the option keeps events ordered by when they happened while preserving the existing behavior by default.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
While integrating PostHog into an app, with themselves as the only user so far, a user watches incoming events in posthog-live. Events sometimes show up out of order: the list follows the order events reach the terminal, not the order they happened.
Describe the solution you'd like
An option in posthog-live to keep the event list sorted by when each event happened, for development use where only a few events arrive at a time.
Describe alternatives you've considered
The Activity tab in PostHog lists events by timestamp, but the user finds it too noisy for this.
Additional context
From: https://us.posthog.com/project/2/support/tickets/81610
- Dominant language
- Python
- Stars
- 40.8k
- Forks
- 3.6k
- Avg merge
- 6h 43m
- Merged PRs (30d)
- 254
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 PostHog/posthog
-
self-driving
Difficulty 1/5 Under an hour Newbie friendliness 74/100
PostHog/posthog#136106 · 1 comment ·
Maintainers usually reply within 1 day
-
Dashboards: selecting a SQL variable value equal to its default is dropped when the dashboard saved another valuePossibly taken @Inf1mum claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
PostHog/posthog#132024 · 1 comment ·
Maintainers usually reply within 1 day
-
self-driving
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PostHog/posthog#130181 · 2 comments ·
Maintainers usually reply within 1 day
-
posthog-cli api: `call`, `info` and `search` read `--help` as a tool namePossibly taken @lazerg claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
PostHog/posthog#129166 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PostHog/posthog#128849 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/kernels#1006 ·
Maintainers usually reply within 1 day
-
precond_kda (new op, #1552) backward kernels hit CUDA illegal memory access on Blackwell under triton 3.3.1, pass under triton 3.7.1Possibly taken @YYuJLiu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fla-org/flash-linear-attention#1749 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bridgecrewio/checkov#7804 ·
Maintainers usually reply within 2 days
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentscope-ai/agentscope#4068 ·
Maintainers usually reply within 2 days