azure-sdk-for-python
azure-sdk-for-python copied to clipboard
Azure
Typo in Python Tables Storage error message
There are two tests for invalid table names in tables storage failing in Python - async test, sync test
We are testing with a list of invalid storage table names, some are failing("1table", "a//", "my_table"), not all of them.
Here's one of the response we got:
'message': 'The specifed resource name contains invalid characters.\n' 'RequestId:6783e6ea-a002-006a-3c48-c912e9000000\n' 'Time:2022-09-15T21:15:28.7300879Z\n' 'ErrorCode:InvalidResourceName'
You can find there's a typo in response message so that we can't catch it and convert it to a ValueError to users.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @klaaslanghout.
Issue Details
There are two tests for invalid table names in tables storage failing in Python - async test, sync test
We are testing with a list of invalid storage table names, some are failing("1table", "a//", "my_table"), not all of them.
Here's one of the response we got:
'message': 'The specifed resource name contains invalid characters.\n' 'RequestId:6783e6ea-a002-006a-3c48-c912e9000000\n' 'Time:2022-09-15T21:15:28.7300879Z\n' 'ErrorCode:InvalidResourceName'
You can find there's a typo in response message so that we can't catch it and convert it to a ValueError to users.
| Author: | YalinLi0312 |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
The typo exists for a while, it breaks all of our live pipelines. Please give some priorities to fix it.
@YalinLi0312 to help me understand better, do you mean this is a service issue? Or a storage issue?
Thanks.
@YalinLi0312 to help me understand better, do you mean this is a service issue? Or a storage issue?
Thanks.
The typo exists in the error message which returned from service end, I need service team to help to resolve it.
Thanks for the clarification.
Given it is not a bug in SDK, we can close the issue or if you want, use the issue to track the service change request (let's update the title to make it clearer that this is used to track the issue).
Hi @klaaslanghout, I find you as the bot tagged your name above. I know you were working on Storage from your GitHub description, do you know anyone in Storage team that can help to resolve this issue?