influxdata / influxdata/chronograf
Chronograf (1.10.1) Cannot read properties of undefined (reading 'ast')
- 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 read properties of undefined (reading 'ast')
at Di.onNotify [as mapToProps] (http://localhost:8888/index.c5ba09e6.js:107:459015)
at r (http://localhost:8888/index.c5ba09e6.js:82:368232)
at r.mapToProps (http://localhost:8888/index.c5ba09e6.js:82:368351)
at r (http://localhost:8888/index.c5ba09e6.js:82:368214)
at http://localhost:8888/index.c5ba09e6.js:82:369625
at http://localhost:8888/index.c5ba09e6.js:82:366831
at Object.useMemo (http://localhost:8888/index.c5ba09e6.js:1:114238)
at _ (http://localhost:8888/index.c5ba09e6.js:1:48864)
at h (http://localhost:8888/index.c5ba09e6.js:82:366775)
at ui (http://localhost:8888/index.c5ba09e6.js:1:109386)
```
Contributor guide
Research direction
The report only identifies the bundled index.c5ba09e6.js stack from Chronograf 1.10.1 and omits the browser, operating system, and reproduction steps. First collect those details and reproduce the TypeError; use the onNotify/mapToProps stack location to trace the failing UI path. Done means the triggering workflow is identified and no longer produces the undefined ast error.
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
- 20/100