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

Cell fails to show properly after creation #18312

Closed
NULLx76 opened this issue May 31, 2020 · 3 comments · Fixed by #18632
Closed

Cell fails to show properly after creation #18312

NULLx76 opened this issue May 31, 2020 · 3 comments · Fixed by #18632
Assignees
Labels
kind/bug severity/sev-3 team/ui v2-prod-bug Trying to track all issues in V2 Prod to check code quality

Comments

@NULLx76
Copy link

NULLx76 commented May 31, 2020

Steps to reproduce:

  1. Create a new query under Explore
  2. Save it to a specific dashboard

Expected behavior:
I expect it to show the cell properly

Actual behavior:
It shows an error message saying I should report a bug. After refreshing it shows up fine though.

This behaviour is consistent over the few times I've tested it.

Environment info:

  • System info: Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64
  • InfluxDB version: InfluxDB 2.0.0-beta.10 (git: d00706dea8) build_date: 2020-05-31T19:20:37Z
  • Browser: Firefox on Linux

Logs:
From the browser console:

Empty string passed to getElementById(). 235 Popover.tsx:217:35
Empty string passed to getElementById(). Overlay.tsx:60:33
Empty string passed to getElementById(). 2 Popover.tsx:217:35
Empty string passed to getElementById(). Overlay.tsx:60:33
Empty string passed to getElementById(). 11 Popover.tsx:217:35
TypeError: can't access property "map", t.queries is undefined
    no TimeSeries.tsx:317
    Redux 7
    React 11
    Redux 11
    u queryStringConfig.ts:9
    o resizeLayout.ts:9
    Redux 3
    B thunks.ts:355
    Redux 2
    getResourceDetails GetResource.tsx:51
    componentDidMount GetResource.tsx:43
    componentDidMount GetResource.tsx:42
    React 3
    unstable_runWithPriority scheduler.production.min.js:18
    React 7
    _unlisten Router.js:103
    r createTransitionManager.js:228
    c createTransitionManager.js:83
    b AsyncUtils.js:74
    b AsyncUtils.js:80
    k getComponents.js:6
    k getComponents.js:30
    b AsyncUtils.js:79
    b AsyncUtils.js:78
    k getComponents.js:29
    c createTransitionManager.js:77
    r TransitionUtils.js:74
    runEnterHooks TransitionUtils.js:107
    l createTransitionManager.js:70
    r TransitionUtils.js:74
    runChangeHooks TransitionUtils.js:131
    l createTransitionManager.js:67
    u createTransitionManager.js:45
    l AsyncUtils.js:41
    y AsyncUtils.js:51
    j matchRoutes.js:231
    u createTransitionManager.js:41
    r createTransitionManager.js:222
    g useQueries.js:75
    d useBasename.js:67
    y createHistory.js:55
    y createHistory.js:54
    C createHistory.js:115
    w createHistory.js:90
    l AsyncUtils.js:51
    loopAsync AsyncUtils.js:55
    w createHistory.js:80
    C createHistory.js:100
    t BrowserProtocol.js:53
    ___hb honeybadger.js:466
    t honeybadger.js:633
    addEventListener DOMUtils.js:5
    startListener BrowserProtocol.js:56
    y createBrowserHistory.js:68
    _ createBrowserHistory.js:84
    d useBasename.js:66
    g useQueries.js:74
    1 index.tsx:172
    Webpack 5
react-dom.production.min.js:198:194
Context that would have been sent to HoneyBadger: errors.ts:50:4
console.table() errors.ts:51:4
(index)
Values
user_id
05c1c665600a9000
orgID
05c1c66578ca9000
deleteWithPredicate
false
downloadCellCSV
false
telegrafEditor
false
customCheckQuery
false
matchingNotificationRules
false
demodata
false
fluxParser
false
frontendExample
42
component
Connect(withRouter(to))

Screenshot of the error:
image

@desa
Copy link
Contributor

desa commented Jun 5, 2020

@NULLx76 Would it be possible for you to provide the JSON of your dashboard. This should be available by opening your network tab in your browser and viewing the dashboard(s) response.

@NULLx76
Copy link
Author

NULLx76 commented Jun 5, 2020

This is the response from a get request to /api/v2/dashboards
get_dashboard.json.txt

and this is the exported dashboard:
export.json.txt

@asalem1 asalem1 added the v2-prod-bug Trying to track all issues in V2 Prod to check code quality label Jun 11, 2020
@asalem1
Copy link
Contributor

asalem1 commented Jun 11, 2020

@NULLx76 it doesn't seem like there were any errors in the logs you linked through to us. Do you happen to know if the issue still exists / whether the issue went away after rerendering the dashboard? I'm also curious as to whether you were referencing any variables in that cell's query?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug severity/sev-3 team/ui v2-prod-bug Trying to track all issues in V2 Prod to check code quality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants