You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use compose-builder command make run no-secty ds-virtual to bring up EdgeX system
on edgex-go:
- make docker-fuzz
- make fuzz-test-command to run fuzzing test on core-command
You will see checker_500 error logs in folder "/edgex-go/fuzz_test/fuzz_results/core-command/FuzzLean/RestlerResults/experiment113/bug_buckets"
Or you can reproduce this problem using postman: PUThttp://localhost:59882/api/v3/device/name/Random-Boolean-Device/Bool
raw JSON "false" into the body
fixed fuzzing core-command http error 500 when invalid input in body http://localhost:59882/api/v3/device/name/Random-Boolean-Device/Bool
Closes: edgexfoundry#4639
Signed-off-by: Valina Li <valina.li@intel.com>
vli11
added a commit
to vli11/edgex-go
that referenced
this issue
Aug 16, 2023
fixed fuzzing core-command http error 500 when invalid input in body http://localhost:59882/api/v3/device/name/Random-Boolean-Device/Bool
Closes: edgexfoundry#4639
Signed-off-by: Valina Li <valina.li@intel.com>
🐞 Bug Report
Affected Services [REQUIRED]
core-command
Is this a regression?
No
Description and Minimal Reproduction [REQUIRED]
use compose-builder command
make run no-secty ds-virtual
to bring up EdgeX systemon edgex-go:
- make docker-fuzz
- make fuzz-test-command to run fuzzing test on core-command
You will see checker_500 error logs in folder "/edgex-go/fuzz_test/fuzz_results/core-command/FuzzLean/RestlerResults/experiment113/bug_buckets"
Or you can reproduce this problem using postman:
PUT
http://localhost:59882/api/v3/device/name/Random-Boolean-Device/Bool
raw JSON "false" into the body
🔥 Exception or Error
http status code 500
Postman error:
{
"apiVersion": "v3",
"message": "failed to parse request body",
"statusCode": 500
}
🌍 Your Environment
Deployment Environment:
EdgeX Version [REQUIRED]:
3.1.0 or v3
Anything else relevant?
The text was updated successfully, but these errors were encountered: