-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[monitor-query] Batch queries will occasionally fail to deserialize due to an incorrectly formatted response body #15688
Comments
CC: @srnagar, @pakrym , @rakshith91 |
Same issue, but with the .net SDK: Azure/azure-sdk-for-net#21655 |
The Log Analytics service has a bug where it sometimes returns the batch query output encoded twice. The issue is still under investigation (Azure#15688) but in the meantime this workaround will enable people to use the API, which is critical since we're in preview. Mitigation for Azure#15688
Adding @KarishmaGhiya, as this is an active bug that will require changes later. |
Yay!! Finally able to reproduce this in python |
There is a workaround currently in main from #15718. Remove once this is solved from the service side. |
Service team is aware, but no ETA on the fix. Moving to backlog |
Hi @richardpark-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
The service (randomly) will return an improperly formatted body for a batch request.
Example:
The request we sent:
The response, with the body seeming to be double-serialized:
In contrast, here the body of a response when things succeed:
The first one appears to have double-encoded the 'body' field, essentially, so it doesn't deserialize properly in the client.
The text was updated successfully, but these errors were encountered: