Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Select: Warning Maximum update depth exceeded.
See original GitHub issueUpdated to the latest v2.17 and am seeing the following warning when opening the Drop on a Select component;
Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render. at InfiniteScroll (https://p86yu.csb.app/node_modules/grommet/es6/components/InfiniteScroll/InfiniteScroll.js:21:23)
Here’s a Codesandbox reproducing the issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
These two useEffects seem to be entering into an infinite loop. Each have dependencies of
pendingLengthwhich gets set in each, which then satisfies the dependency condition as well as the checks within the useEffects. Seems like we need to add an additional condition aroundpendingLength.This may have been fixed by #5636 . Select uses InfiniteScroll for its options and had an infinite recursion with onMore when the list of items was empty.