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

Unable to run timeline demo page #58

Open
MattIGolden opened this issue Mar 20, 2020 · 2 comments
Open

Unable to run timeline demo page #58

MattIGolden opened this issue Mar 20, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@MattIGolden
Copy link
Contributor

Description

Screen Shot 2020-03-19 at 8 54 41 PM

I am trying to open the timeline demo but I get an error page every time I try. This is the only page that isn't working as it should for me. All the other (detail panel, empty state, etc.) are fine.
Here are some steps I took to fix this issue.

  • Updated the NR1 CLI

  • Double checked to make sure my fork was up to date with upstream repo

  • Been sure to nom install in both the root and demo directories

  • I’ve closed and reopened the nerdlet via the launcher on the homepage

  • And finally restarted my computer and started up the project again and still I’m getting the following errors when I try to open the timeline page

Steps to Reproduce

Go into the nr1-community nerdpack and navigate to the timeline demo.

Expected Behaviour

It should look like the rest of the other pages do when I click into it.

Relevant Logs / Console output

There are five errors in the console. A detailed log is below.

Your Environment

  • NR1 CLI version used: 10.16.3
  • Browser name and version: Chrome 80.0.3987.132 (Official Build) (64-bit)
  • Operating System and version: Mac Os Mojave 10.14.6

Additional context

Below are the following errors I'm receiving in the console.

    at BasicExample.render (b1ec85b5-c8c4-41f4-bfa1-f1618fb1b48e--nr1-community-demo-nerdlet.js:7899)
    at finishClassComponent (react-dom.development.js:14425)
    at updateClassComponent (react-dom.development.js:14388)
    at beginWork (react-dom.development.js:15206)
    at performUnitOfWork (react-dom.development.js:17944)
    at workLoop (react-dom.development.js:17984)
    at HTMLUnknownElement.callCallback (react-dom.development.js:143)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:193)
    at invokeGuardedCallback (react-dom.development.js:250)
    at replayUnitOfWork (react-dom.development.js:17231)

- The above error occurred in the <BasicExample> component:
    in BasicExample (at Timeline/index.js:125)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at Timeline/index.js:111)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at Timeline/index.js:110)
    in TimelineDemo (at nr1-community-demo-nerdlet/index.js:191)
    in main (at nr1-community-demo-nerdlet/index.js:190)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at nr1-community-demo-nerdlet/index.js:189)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at nr1-community-demo-nerdlet/index.js:147)
    in NerdpackLayoutStandard
    in t

React will try to recreate this component tree from scratch using the error boundary you provided, t

- Warning: t: Error boundaries should implement getDerivedStateFromError(). In that method, return a state update to display an error message or fallback UI.
- Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in AccountDropdown (at basic.js:80)
    in div (at basic.js:73)
    in BasicExample (at Timeline/index.js:125)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at Timeline/index.js:111)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at Timeline/index.js:110)
    in TimelineDemo (at nr1-community-demo-nerdlet/index.js:191)
    in main (at nr1-community-demo-nerdlet/index.js:190)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at nr1-community-demo-nerdlet/index.js:189)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at nr1-community-demo-nerdlet/index.js:147)
    in NerdpackLayoutStandard

- Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in KitchenSinkExample (at Timeline/index.js:126)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at Timeline/index.js:111)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at Timeline/index.js:110)
    in TimelineDemo (at nr1-community-demo-nerdlet/index.js:191)
    in main (at nr1-community-demo-nerdlet/index.js:190)
    in div (created by t)
    in t (created by GridItem)
    in GridItem (at nr1-community-demo-nerdlet/index.js:189)
    in div (created by t)
    in t (created by t)
    in t (created by Grid)
    in Grid (at nr1-community-demo-nerdlet/index.js:147)
    in NerdpackLayoutStandard
@MattIGolden MattIGolden added the bug Something isn't working label Mar 20, 2020
@tangollama
Copy link
Contributor

@danielgolden can you look into this next week?

@danielgolden
Copy link
Contributor

@tangollama I think the issue here is that he doesn't have any account data for the timeline component to use. It loads fine for me, but in my case it's using demotron v2. Is there any way around this?

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

No branches or pull requests

3 participants