Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug: better resolution on fetch errors #363

Open
SgtPooki opened this issue Jun 3, 2023 · 0 comments
Open

bug: better resolution on fetch errors #363

SgtPooki opened this issue Jun 3, 2023 · 0 comments
Labels
effort/hours Estimated to take one or several hours exp/beginner Can be confidently tackled by newcomers good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/design-ux UX strategy, research, not solely visual design

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Jun 3, 2023

When fetching content that can't be found, you have to reload the page. This shouldn't be required.

from @aschmahmann:

  • Once you start loading the eth blocks you can’t load anything else until you refresh
    • Likely true for any other “stressed” lookup which overtime causes sluggishness + hanging
    • Same with what happens if you try and load a block that isn’t discoverable, it eats up all the resources

NOTE: eth codec and blocks were removed, but problem is related to the page not rendering some fallback view when fetch fails. It should instead stop all node fetching and present user with "Okay, take me back to start exploring page" or similar.
@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Jun 3, 2023
@github-project-automation github-project-automation bot moved this to Needs Grooming in IPFS-GUI (PL EngRes) Jun 3, 2023
@SgtPooki SgtPooki added kind/bug A bug in existing code (including security flaws) help wanted Seeking public contribution on this issue good first issue Good issue for new contributors P1 High: Likely tackled by core team if no one steps up topic/design-ux UX strategy, research, not solely visual design exp/beginner Can be confidently tackled by newcomers effort/hours Estimated to take one or several hours status/ready Ready to be worked and removed need/triage Needs initial labeling and prioritization labels Jun 5, 2023
@SgtPooki SgtPooki moved this from Needs Grooming to Needs Prep Work / Blocked in IPFS-GUI (PL EngRes) Jun 5, 2023
@SgtPooki SgtPooki mentioned this issue Jun 5, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/hours Estimated to take one or several hours exp/beginner Can be confidently tackled by newcomers good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/design-ux UX strategy, research, not solely visual design
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Needs Prep Work / Blocked
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SgtPooki