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.

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

INFO: 127.0.0.1:9968 - "POST /api/box HTTP/1.1" 422 Unprocessable Entity #3

Open
biaggii opened this issue Apr 18, 2023 · 6 comments
Open

Comments

@biaggii
Copy link

biaggii commented Apr 18, 2023

INFO: 127.0.0.1:9968 - "POST /api/box HTTP/1.1" 422 Unprocessable Entity

@Kingfish404
Copy link
Owner

more info needed to debug, such as shell output from both server.py and node.js, the image that uploads

@bensonbs
Copy link

got same error INFO: 127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity

server.py

(meta) PS C:\Users\ZME\AI\segment-anything-webui> python scripts/server.py
device: cuda
100%|███████████████████████████████████████| 335M/335M [04:53<00:00, 1.20MiB/s]
INFO:     Started server process [5912]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
INFO:     127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity
INFO:     127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity

node.js

(base) PS C:\Users\ZME\AI\segment-anything-webui> npm run dev

> [email protected] dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

event - compiled client and server successfully in 1612 ms (170 modules)
wait  - compiling...
event - compiled successfully in 76 ms (137 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 123 ms (183 modules)
wait  - compiling /_error (client and server)...

@Kingfish404
Copy link
Owner

got same error INFO: 127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity

server.py

(meta) PS C:\Users\ZME\AI\segment-anything-webui> python scripts/server.py
device: cuda
100%|███████████████████████████████████████| 335M/335M [04:53<00:00, 1.20MiB/s]
INFO:     Started server process [5912]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
INFO:     127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity
INFO:     127.0.0.1:3938 - "POST /api/point HTTP/1.1" 422 Unprocessable Entity

node.js

(base) PS C:\Users\ZME\AI\segment-anything-webui> npm run dev

> [email protected] dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

event - compiled client and server successfully in 1612 ms (170 modules)
wait  - compiling...
event - compiled successfully in 76 ms (137 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 123 ms (183 modules)
wait  - compiling /_error (client and server)...

Which version of the Node and Python

@bensonbs
Copy link

Node.js v19.2.0
python 3.9.16

@Kingfish404 Kingfish404 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2023
@wizardpisces
Copy link

Same Error , any progress?
Node.js v18.17.1
Python 3.10.11

@Kingfish404 Kingfish404 reopened this Mar 22, 2024
@Kingfish404
Copy link
Owner

Unfortunately, I can't reproduce this issue (Linux, macOS, Windows 11). It is recommended to use docker to start the project, or provide a docker image that could reproduce this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants