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

Name not resolved errors not caught #123

Closed
rhiaro opened this issue Jan 27, 2016 · 1 comment
Closed

Name not resolved errors not caught #123

rhiaro opened this issue Jan 27, 2016 · 1 comment
Labels
error-handling

Comments

@rhiaro
Copy link
Contributor

rhiaro commented Jan 27, 2016

In places a URL is entered as a string by the user, if it's not a real tld, or it exists (not 404) but has a server/DNS misconfiguration (or something) that makes it unreachable, the result is Error: Name Not Resolved. I haven't figured out how to catch these from simpleRDF's GET yet, but we need to deal with these as the only feedback is in the console right now.
@csarven
Copy link
Collaborator

csarven commented Apr 23, 2024

Closing issue in favour of more specific #384 - same same but different.

@csarven csarven closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
error-handling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@csarven @rhiaro