Michael Matloka

## Is your feature request related to a problem? It's common to set up a funnel ending with some sort of purchase or payment event. In these cases it could...

fix(support): Show new tickets as "New"

4

## Problem Unhandled Zendesk tickets (those without a reply or note in Zendesk) currently show up as "Open", which blends in with tickets awaiting _further_ activity from the team. This...

Fixes #567! Happy to improve based on feedback.

Store dark mode in cross-subdomain cookie

1

Reverts PostHog/posthog.com#8145

feat(insights): Make all queries cacheable

9

## Problem Currently `HogQLQuery` and `EventsQuery` aren't cached in any way, which is pretty bad in terms of loading dashboards. If there is a specific reason for this, absolutely let...

ci: Run core backend tests with both HogQL and legacy insights

1

## Changes Let's make the HogQL engine the default. Still leaving a strategy with the legacy engine running. This will allow us to catch problems in the saved insights/dashboards layer,...

chore(dev): Add Flox for local environment setup

2

## Problem To get started developing PostHog, you have to install a bunch of dependencies and run a series of commands from the [Developing locally](https://posthog.com/handbook/engineering/developing-locally) guide. What if there was...

[PostHog](https://posthog.com/) is a much better alternative to storing logs in a Postgres table, in performance and in ease of use. Note: existing data will need to be backfilled into PostHog.

fix(insights): Support dashboard filters in ActorsQuery

3

## Changes Resolves [this Sentry issue](https://posthog.sentry.io/issues/5236763612/events/7932e7f070f14e10b786218d17313616/?project=-1&query=is%3Aunresolved+transaction%3A%2Fapi%2Fprojects%2F%7Bparent_lookup_team_id%7D%2Finsights%2F%7Bpk%7D%2F&referrer=previous-event&statsPeriod=7d&stream_index=2&utc=true).

fix(insights): Make async query execution use the same cache as sync

5

## Problem When a query is executed async (via `/query/`), we aren't able to reuse its results in sync execution (`/insights/` or `/dashboards/`), because we treat `LimitContext.QUERY` and `LimitContext.QUERY_ASYNC` as...