-
Notifications
You must be signed in to change notification settings - Fork 502
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
fix: handle ipfs.files.stat RPC error responses #2327
base: main
Are you sure you want to change the base?
Conversation
Thank you for submitting this PR!
Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. |
@lidel Can you review the PR and suggest any changes if needed, and guide me if I'm heading in the right direction? |
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.
I am afraid this does not fix the problem from #2299. See repro steps in #2299 (comment). When I simulate them, local dev server started with npc ci && npm start
produces:
And no toaster with error is displayed.
I think if ipfs.files.stat
for /
occurs, and error includes value of Tsize is too large
we should not only display toaster notification, but extend error message with suggestion that user should restart their node.
Fixes #2299