-
Notifications
You must be signed in to change notification settings - Fork 2.9k
console: add ErrorBoundary for VoyagerView and fix memory requirements of viz.js (close #4818) #4856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
this will eventually end up enclosing the VoyagerView component
This comment has been minimized.
This comment has been minimized.
|
Sameer Kolhar seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Deploy preview for hasura-docs ready! Built with commit 4a85374 |
|
Review app for commit bc66ec4 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
|
Review app for commit d56f820 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
kolharsam
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@beerose have updated the component to TS.
|
Review app for commit 63da193 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
|
Review app for commit c68f6cd deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
|
Review app for commit f456ff2 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
|
Review app for commit a02dce3 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
|
Review app for commit 6a5698c deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
console/src/components/Services/Common/ComponentErrorBoundary.tsx
Outdated
Show resolved
Hide resolved
|
Review app for commit 25eba42 deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
|
Review app for commit f61a73e deployed to Heroku: https://hge-ci-pull-4856.herokuapp.com |
Changelog
CHANGELOG.mdis updated with user-facing content relevant to this PR.Affected components
Related Issues
#3023, should fix #4818
Solution and Design
The design is the same as the
RuntimeErrorcomponent, as suggested in #4818 one of the solutions is an Error Boundary specifically for theVoyagerViewcomponent. Which, now, has been implemented.[x] Next would be to try and get to the root of the problem on theVoyagerViewThe main problem being that for larger schema's and tables, the visualizer runs out of memory on the stack and so we had to rectify that by increasing the stack memory and buffer memory that is allocated to
viz.jsfor rendering the graphSteps to test and verify (to be changed)
First make 40+ tables on theGraphQL consoleVoyagerErrBoundarycomponent if an error does occur. ~~Error screen
