Skip to content
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.

Helpful gateway errors #21

Closed
3 tasks
ghost opened this issue Mar 10, 2017 · 3 comments
Closed
3 tasks

Helpful gateway errors #21

ghost opened this issue Mar 10, 2017 · 3 comments
Milestone
The Docs are less...

Comments

@ghost
Copy link

ghost commented Mar 10, 2017

Errors and timeouts on the gateway are way too obscure. Even something as simple as a 404 sounds scary: "Path Resolve error: no link named "foo" under Qmdf6iGuPoQ7jmGM48nWoy46F5EwMiXYVif968cpwQXDrU".

We can make these a lot more friendly and useful for seeing how ipfs works. (And just nicer to debug.)
@flyingzumwalt flyingzumwalt modified the milestone: The Docs are Not a Disaster Mar 10, 2017
@ghost ghost added the tools label Mar 10, 2017
@hsanjuan hsanjuan assigned hsanjuan and unassigned hsanjuan Mar 13, 2017
@hsanjuan
Copy link
Member

I might try to extract gateway to it's own repo. Is this as easy as it sounds @lgierth ?

@ghost
Copy link
Author

ghost commented Mar 13, 2017

Yeah it should be straightforward once the core-api has patch add-link, rm-link, and set-data, which I'll to first thing this sprint (in fact reviving this work right now).

Cool 👍

@ghost
Copy link
Author

ghost commented Jan 10, 2018

This continues to be tracked in ipfs/go-ipfs-gateway#5

@ghost ghost closed this as completed Jan 10, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
The Docs are less confusing
Development

No branches or pull requests
2 participants
@flyingzumwalt @hsanjuan