Skip to content
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

Dashboard not rendering funnel #3574

Closed
1 of 2 tasks
kpthatsme opened this issue Mar 4, 2021 · 1 comment
Closed
1 of 2 tasks

Dashboard not rendering funnel #3574

kpthatsme opened this issue Mar 4, 2021 · 1 comment
Assignees
Labels
bug Something isn't working right

Comments

@kpthatsme
Copy link
Contributor

kpthatsme commented Mar 4, 2021

Bug description

This dashboard fails to render the step funnel in the top left, showing an error message.

Clicking into the funnel it works and loads properly.

Attempting to re-add to the dashboard occasionally works, but ends up making the other funnel (trend) chart not render.

Screen Shot 2021-03-03 at 6 19 58 PM

I think this has to do with showing multiple types of funnels on a single dashboard i.e. trends vs. steps.

It looks like either the trends or the steps funnels will successfully render but not both.

Expected behavior

  • I expect all valid funnels on the dashboard to render

How to reproduce

  1. Visit the dashboard, 'Core Funnel' isn't rendered
  2. Click into the funnel and it should render fine on the insights view

I think this might be something with showing a mixture of funnels with trends and steps? It seems like either one of those will load i.e. all the step funnels render properly or all the trend ones, but never both.

Environment

  • PostHog Cloud
  • self-hosted PostHog, version/commit: please provide

Additional context

I did see this in my JS console:

In order to be iterable, non-array objects must have a [Symbol.iterator]() method.
    at e.exports (nonIterableSpread.js:2)
    at e.exports (toConsumableArray.js:10)
    at LineGraph.js:145
    at Array.map (<anonymous>)
    at LineGraph.js:143
    at LineGraph.js:65
    at ac (react-dom.production.min.js:211)
    at ms (react-dom.production.min.js:257)
    at t.unstable_runWithPriority (scheduler.production.min.js:19)
    at Ia (react-dom.production.min.js:122)
    at vs (react-dom.production.min.js:257)
    at Zc (react-dom.production.min.js:239)
    at react-dom.production.min.js:123
    at t.unstable_runWithPriority (scheduler.production.min.js:19)
    at Ia (react-dom.production.min.js:122)
    at qa (react-dom.production.min.js:123)
    at Wa (react-dom.production.min.js:122)
    at $c (react-dom.production.min.js:230)
    at Object.enqueueSetState (react-dom.production.min.js:132)
    at s._.setState (react.production.min.js:12)
    at WidthProvider.js:99
    at r (helpers.js:72)
    at q (utils.tsx:268)
    at r (helpers.js:72)```

####  *Thank you* for your bug report – we love squashing them!
@kpthatsme kpthatsme added the bug Something isn't working right label Mar 4, 2021
@kpthatsme kpthatsme added this to the Core Experience - Bugs / UX Improvements milestone Mar 11, 2021
@kpthatsme kpthatsme removed this from the Core Experience - Bugs / UX Improvements milestone Mar 12, 2021
@kpthatsme kpthatsme self-assigned this Mar 12, 2021
@kpthatsme
Copy link
Contributor Author

Fixed in #3641

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working right
Projects
None yet
Development

No branches or pull requests

1 participant