From our inbox

The dashboards scout compared the Signals pipeline dashboard against the data it could plot. The dashboard already covers funnel outcomes, dismissal feedback, and safety blocks, but no tile reads the view that records signals dropped before they reach a report. A drop in one source could grow for days before anyone noticed.

pganalyze flags a slow read on the activity log table. The notification feed filters a team's whole history by a very selective set of scope and item pairs, then takes the 10 newest rows, so the ordered walk reads far down the history before it fills one page. The same request also fires several near-identical unbounded reads over the table. Nobody sees an error, just a slow bell, and the cost grows with every team's history.

While checking its own coverage, the logs scout found that almost all PostHog AI log lines come from a background worker service, not the web service its instructions tell it to read. Its main query only reads the web service, so it cannot see new log patterns or rate changes where most of the traffic actually lands. The web service still writes some scoped error lines, so it stays useful too.

In the desktop app, WorkColumn calls selectedTaskIds.includes(item.id) inside the loop that renders each row. The selection is a plain array, so every lookup is linear, and a long list with many selected items does quadratic work on each render. The selection hook already builds a Set for filtering, so the fix has a pattern to follow.

A burst of users opening the similar issues panel got a 500 instead of a 400. The similar issues query runner passes the issue id straight into a Django ORM filter, and the query API only maps DRF validation errors to a 400. It is the only error tracking runner that skips the shared validate_uuid_param guard its four siblings call. A second, quieter problem sits in the same runner: a correct 404 for an issue with no fingerprints counts against the query SLO and gets captured as an error.

A GitHub issue reported that adding a new line to an Inbox refund note submits the form. Once a reason is selected, both Enter and Shift+Enter reach the form's submit handler. The investigation found that the note field lacks the keyboard event guard already used by the dismiss dialog.