-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Funnels endpoint failing on posthog + postgresql #6530
Labels
bug
Something isn't working right
Comments
It looks as though the I'll add a test and hopefully that will highlight the issue. |
hazzadous
pushed a commit
that referenced
this issue
Oct 19, 2021
) * Revert "perf(funnels): add filter on pdi.team_id to speed up query (#5997)" This merged caused an issue with the funnels endpoint when display was set to `ActionsLineGraph` I'm reverting so we can add in a snapshot test that will fail when this revert is reverted. This reverts commit 2fb7cf8. * test(funnel): add snapshot test for funnel trend query for postgres This test just checks the Funnel with `display="ActionsLineGraph"` against what it previously did before #5997 was merged. This code path was previously untested, so the issue wasn't picked up and resulted in #6530 * Revert "Revert "perf(funnels): add filter on pdi.team_id to speed up query" Now that we have a test in place for #6530 I'm reverting this revert so we can implement a fix. This reverts commit 49761a3. * only test on postgres * fix(funnel): `TypeError` for funnel with display=ActionsLineGraph This resolves an issue what was introduced by #5997 where we would fail to calculate a funnel result if display="ActionsLineGraph" was specified. The fix was simply to wrap a string in `sql.SQL`. Resolves #6530 * fix import order * move test outside of test factory * remove imports * move test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
A posthog user has been experiencing a crash that requires them to run
docker restart
to get things working again. The slack user discussion of this is hereThe error message they are seeing is:
From the traceback it looks like this is specifically caused when the url query param is set to
ActionsLineGraph
Expected behavior
A couple of oddities here:
More investigation required
How to reproduce
TBC
Environment
Additional context
Thank you for your bug report – we love squashing them!
The text was updated successfully, but these errors were encountered: