iyaja / llama-fs

A self-organizing file system with llama 3
MIT License
4.49k stars 259 forks source link

Method not allowed #2

Open Rathna-K opened 1 month ago

Rathna-K commented 1 month ago

When I run it and post a request for scan, I am getting Method not allowed for POST !

iraadit commented 1 month ago

Following the README, getting the same error

{"detail":"Method Not Allowed"}

INFO: 127.0.0.1:57552 - "POST / HTTP/1.1" 405 Method Not Allowed

bsmartt13 commented 1 month ago

check ze docs boys / only allows GET, look through the docs as the source of truth on what apis support what methods. try to line that up against the readme.md insofar as it's possible, tweak that curl example and you might get there.

however, passing in my downloads folder made the server start dumping 401s and eventually curl exited with 500 internal error. this is more of a POC than something that might be robust and stable.

lightningorb commented 1 month ago

@bsmartt13 this is from the example on the README.md which people use as their first point of entry into RTFM.

bsmartt13 commented 1 month ago

@lightningorb right readme != docs. http://127.0.0.1:8000/docs let me spell it out POST to /batch not /

ArjixWasTaken commented 1 month ago

@bsmartt13 in this specific scenario you are correct, but the README is often the best documentation you can find on random projects like this

anujmodi1 commented 1 month ago

Even If I execute the /batch post command at http://127.0.0.1:8000/docs, am still getting the same error message. 500 | Error: Internal Server Error

while on the cli, INFO: 127.0.0.1:64039 - "POST /batch HTTP/1.1" 500 Internal Server Error ERROR: Exception in ASGI application Traceback (most recent call last): IndexError: list index out of range

ArjixWasTaken commented 1 month ago

@anujmodi1

"Internal Server Error" means the server had an uncaught error, or it entered an unexpected state this is 100% most likely a bug and should be reported on a new issue

bsmartt13 commented 1 month ago

@anujmodi1 500 Internal server error is not the issue described in issue here. Please check that you are using A valid api key before opening a different issue.

IMO, at least tbis 500 should be handled more gracefully.