Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] DeviceUpdate Delete recording appears incorrect
See original GitHub issueLibrary name and version
Azure.ResourceManager.DeviceUpdate
Describe the bug
In the response to the DELETE request, the response body is null, but the content-length is 4. It’s not clear if this is a service issue or an issue with the recording, but the content-length and the response body are not consistent. It seems like the “4” might be coming from the length of null, but the null value would not be treated as a string by the Test Framework, and the content-length should probably either be 0 or not present.
I tried re-recording to debug and see what is causing this, but the test-resources script did not create usable resources.
Expected behavior
Content-Length and response body should be consistent.
Actual behavior
Content-Length and response body are inconsistent.
Reproduction Steps
Run the Delete test from AccountOperationsTests or InstanceOperationsTests.
Environment
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep, you should be able to see the error in Test-Proxy from playback if you check out my branch.
Closed as fixed https://github.com/Azure/azure-sdk-tools/pull/2634