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

"Resource not found" error when uploading file and database is not running #54

Open
safareli opened this issue Jul 7, 2017 · 2 comments
Labels

Comments

@safareli
Copy link
Contributor

safareli commented Jul 7, 2017

Quasar advanced was running, but mongo was not started. In console output was like this

Using metastore: jdbc:h2:file:/Users/safareli/Library/Application Support/quasar/quasar-metastore.db
Warning: Failed to mount '/test/' because 'Connection failed: java.util.concurrent.TimeoutException: Timed out attempting to connect to: [localhost:27017]'.
Server started listening on port 8080

But server was still working.

Then I tried to upload some file, but got error Resource not found:

screen shot 2017-07-07 at 8 43 43 pm

I guess we can say why we can't upload file rather than showing such general error.

@safareli safareli added the bug label Jul 7, 2017
@garyb
Copy link
Member

garyb commented Jul 7, 2017

I think 404 is the correct status here - the resource is unfindable when the database isn't present.

Either way, I don't think this repo is the right place for this issue - it's either an enhancement to quasar to give us more info when this fails (although, did you check to see exactly what the 404 response contained?), or it's an issue for SlamData to display the error message differently.

@safareli
Copy link
Contributor Author

safareli commented Jul 7, 2017

Response contains this:

{ "error": { "status": "Path not found.", "detail": { "path": "/tmp" } } }

The file I'm uploading is not named tmp and "pwd" is /

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants