fix: resolve circular Suspense fallback causing infinite loading in Entropy explorer #2991
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixed a circular Suspense fallback in the Paginator component that was causing infinite loading animations in the Entropy explorer app. The fallback was self-referencing (
<Paginator {...props} />
), preventing the Suspense boundary from ever resolving.Rationale
The Entropy explorer was displaying content correctly but showed a persistent loading animation in the browser. This was caused by the Paginator component's Suspense fallback creating a circular reference - the component was trying to render itself as its own loading fallback, creating an infinite loop that prevented the Suspense from settling.
The fix replaces the self-referencing fallback with
<PaginatorImpl isPending {...props} />
, following the same pattern used by other components in the file (SearchBar, StatusSelect, ChainSelect).How has this been tested?
Manual testing steps:
Reviewer Checklist:
Link to Devin run: https://app.devin.ai/sessions/e89852faa4ea45148c336c6620dcc95c
Requested by: Jayant ([email protected])