influxdata / influxdata/chronograf

Chronograf (1.10.7) Cannot destructure property 'menuOption' of 'Q2.find(...)' as it is undefined.

Open
#6,157 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.6k
Forks
250
Avg merge
1d 3h
Merged PRs (30d)
9

Description

What browser are you using (name and version)?

What operating system are you using?

Please describe what you were trying to do when you encountered this error:

```
TypeError: Cannot destructure property 'menuOption' of 'Q2.find(...)' as it is undefined.
at N3.render (https://tms.whtrading.org:8888/index.602d6942.js:107:358898)
at N3.render (https://tms.whtrading.org:8888/index.602d6942.js:82:652443)
at es (https://tms.whtrading.org:8888/index.602d6942.js:1:121321)
at Ji (https://tms.whtrading.org:8888/index.602d6942.js:1:121116)
at Ms (https://tms.whtrading.org:8888/index.602d6942.js:1:156618)
at Nl (https://tms.whtrading.org:8888/index.602d6942.js:1:148092)
at _l (https://tms.whtrading.org:8888/index.602d6942.js:1:148017)
at bl (https://tms.whtrading.org:8888/index.602d6942.js:1:145047)
at https://tms.whtrading.org:8888/index.602d6942.js:1:96793
at v (https://tms.whtrading.org:8888/index.602d6942.js:1:172695)
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the error in Chronograf 1.10.7 and record the missing browser, operating system, and user action details requested by the issue template. Use the bundled index.602d6942.js stack and N3.render as the initial entry point; done means identifying the triggering flow and confirming that it no longer throws.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.