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
Command
The issue is located in: CommandGET006 - Get specified device read command when ds-returnevent is false
Is this a regression?
Testcase is modified in main branch
Yes, the previous version in which this bug was not present was: ....
Description and Minimal Reproduction [REQUIRED]
It is failing in the step "When Get Device ${device_name} Read Command Virtual_GenerateDeviceValue_Boolean_R With ds-returnevent=false" as in this step they are expecting something in the response body to set a response variable but this should not send any response body as we are making ds-returnevent=false.
Resolving variable '${resp.json()}' failed: JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Yes I have handled it using TRY and CATCH now.. Thanks for pointing the issue
Can you please tell me why we have deleted virtual-profile-sample? because in core command we are creating the devices with virtual-sample-profile.yaml only @cherrycl ?
🐞 Bug Report
Affected Services [REQUIRED]
Command The issue is located in: CommandGET006 - Get specified device read command when ds-returnevent is falseIs this a regression?
Testcase is modified in main branch Yes, the previous version in which this bug was not present was: ....Description and Minimal Reproduction [REQUIRED]
It is failing in the step "When Get Device ${device_name} Read Command Virtual_GenerateDeviceValue_Boolean_R With ds-returnevent=false" as in this step they are expecting something in the response body to set a response variable but this should not send any response body as we are making ds-returnevent=false.
Resolving variable '${resp.json()}' failed: JSONDecodeError: Expecting value: line 1 column 1 (char 0)
🔥 Exception or Error
🌍 Your Environment
Deployment Environment:
EdgeX Version [REQUIRED]:
3.2.. main branch
Anything else relevant?
The text was updated successfully, but these errors were encountered: