easyeda / easyeda/eext-paden-integration
Error: HTTP 错误: 400
- Dominant language
- HTML
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
嘉立创EDA版本:V3.2.149,插件版本V1.0.7
PDN网络电压源负载选择
开始分析后出现Error: HTTP 错误: 400 - {"detail":"There was an error parsing the body"}
小黑窗日志
============================================
paden-service build and start
============================================
Found: python3 Python 3.14.3
[OK] Python Python 3.14.3 (meets 3.10+ requirement)
[1/4] Checking local files...
All required files present
[2/4] Checking dependencies...
All dependencies installed
[3/4] Syntax check...
All syntax checks passed
[4/4] Starting server...
============================================
OK Starting server on port 5000 ...
============================================
Press Ctrl+C to stop the server
INFO: Will watch for changes in these directories: ['D:\\Downloads\\paden-service\\paden-service']
INFO: Uvicorn running on http://0.0.0.0:5000 (Press CTRL+C to quit)
INFO: Started reloader process [43224] using StatReload
INFO: Started server process [39340]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: 127.0.0.1:63827 - "GET /test HTTP/1.1" 200 OK
Expected boundary character 87, got 102 at index 8
INFO: 127.0.0.1:51956 - "POST /analyze-gerber HTTP/1.1" 400 Bad Request
INFO: 127.0.0.1:50509 - "GET /test HTTP/1.1" 200 OK
Expected boundary character 87, got 102 at index 8
INFO: 127.0.0.1:63270 - "POST /analyze-gerber HTTP/1.1" 400 Bad Request
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the PDN analysis request from the reported EasyEDA and plugin versions, then inspect the /analyze-gerber endpoint and its multipart request parsing. Use the logged boundary error to trace the malformed request body. Done means the same analysis request is accepted without HTTP 400 and the parsing error no longer appears in the server log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100