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

Calendar Demo Crash after 10sec on nivo.rocks/calendar #1203

Closed
froger opened this issue Oct 31, 2020 · 1 comment · Fixed by #1214
Closed

Calendar Demo Crash after 10sec on nivo.rocks/calendar #1203

froger opened this issue Oct 31, 2020 · 1 comment · Fixed by #1214

Comments

@froger
Copy link

froger commented Oct 31, 2020

Hello,
Visiting the nivo.rocks website, I encounter an error with the calendar demo, here my report, hope it can help.

Describe/explain the bug
the demo of the calendar component crash after few seconds on the nivo.rocks website.

To Reproduce

Steps to reproduce the behaviour:

  1. Go to https://nivo.rocks/calendar/, don't do any interactions.
  2. Wait more or less 10sec
  3. See error: the screen becomes white

Expected behaviour
The component should stay mounted, and I should be able to interact with the component

Console.log

23:09:13.666 VM268:1 XHR finished loading: GET "https://nivo.rocks/page-data/bubble/page-data.json".
23:09:15.112 react-dom.production.min.js:4454 Invariant Violation: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=null&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. 

Desktop:

  • OS: Mac Mojave
  • Browser Chrome
  • Version 86.0

Thank you, and congrats for this great job! Just starting, already in love.

@wyze
Copy link
Contributor

wyze commented Nov 1, 2020

I wasn't able to reproduce this. Any other information you can provide? What about in an incognito window?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants