influxdata / influxdata/chronograf
Chronograf (1.10.3) Maximum call stack size exceeded
- 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:
```
RangeError: Maximum call stack size exceeded
at http://10.111.2.170:8888/index.61c367c8.js:107:156053
at http://10.111.2.170:8888/index.61c367c8.js:82:971303
at AY.render (http://10.111.2.170:8888/index.61c367c8.js:107:156294)
at es (http://10.111.2.170:8888/index.61c367c8.js:1:121321)
at Ji (http://10.111.2.170:8888/index.61c367c8.js:1:121116)
at Ps (http://10.111.2.170:8888/index.61c367c8.js:1:156618)
at Nl (http://10.111.2.170:8888/index.61c367c8.js:1:148092)
at _l (http://10.111.2.170:8888/index.61c367c8.js:1:148017)
at bl (http://10.111.2.170:8888/index.61c367c8.js:1:145047)
at http://10.111.2.170:8888/index.61c367c8.js:1:96793
```
Contributor guide
Research direction
Start by reproducing the error in Chronograf 1.10.3 and use the stack trace in index.61c367c8.js as the initial entry point. Identify the source component behind the AY.render call and verify that the same action no longer produces a maximum call stack 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