table submit_transaction throws IndexError if there is no transaction

[G-M-twostay]

• Package Name: azure-data-tables:
• **Package Version: 12.4.3 **:
• Operating System: win11 enterprise:
• Python Version: 3.11:

Describe the bug
azure.data.tables.aio.TableClient.submit_transaction throws IndexError if the parameter operations is an empty list or empty iterator.

To Reproduce
Steps to reproduce the behavior:

1. Setup an aio.TableClient. For example, client=TableClient(...).
2. use client.submit_transaction([]).

Expected behavior
Since there is no transaction, I expected this to be a no-op and do nothing.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[kashifkhan]

Thank you for the feedback @G-M-twostay . We will investigate and get back to you asap.

[YalinLi0312]

Hi @G-M-twostay , thanks for reporting the issue! We are fixing it and will prepare a release with the bug fix soon.

[annatisch]

Thanks @G-M-twostay - we have resolved the original deserialization error that was causing the IndexError - this will be released in the next azure-core release in September.
The reason for the IndexError is that the service actually treats this scenario as an error case and returns a 400 "InvalidInput" status code. The deserialization code in Core couldn't match the incoming error response to the outgoing request because the batch of requests was empty. Now that this has been fixed, the error response will be properly deserialized so the updated behaviour in this scenario will be an HttpResponseError rather than an IndexError (This behaviour will now be consistent across both Storage and Cosmos Tables services, as Cosmos was already raising an HttpResponseError in this scenario).