Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Storage: Timstamp's microseconds value out of range #212

Closed
bndw opened this issue Sep 11, 2014 · 3 comments
Closed

Storage: Timstamp's microseconds value out of range #212

bndw opened this issue Sep 11, 2014 · 3 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@bndw
Copy link

bndw commented Sep 11, 2014

The _from_entity_datetime() function was throwing a ValueError exception when using the query_entities() method in TableService. This was caused by the microseconds value being out of range. As shown in the exception below, the microseconds value is greater than 999999.

Exception:

ValueError: time data '2014-09-02T21:09:14.8848547Z' does not match format '%Y-%m-%dT%H:%M:%S.%fZ'
@bndw bndw mentioned this issue Sep 11, 2014
Closed
@huguesv
Copy link
Contributor

huguesv commented Sep 22, 2014

Hi, thanks for taking the time to issue a pull request.

After discussing with some team members, we've decided to take the python-dateutil solution I created a few weeks ago:
#201

If we didn't care about the timezone, we'd take your fix, as it doesn't require any external packages for datetime parsing.

Sorry for the duplicate work :(

@huguesv huguesv added bug This issue requires a change to an existing behavior in the product in order to be resolved. Storage Storage Service (Queues, Blobs, Files) labels Sep 22, 2014
@bndw
Copy link
Author

bndw commented Sep 26, 2014

No worries, thanks for the explanation.

@huguesv
Copy link
Contributor

huguesv commented Nov 24, 2014

Fix available in v0.9

@huguesv huguesv closed this as completed Nov 24, 2014
@bsiegel bsiegel added the Service Attention This issue is responsible by Azure service team. label Sep 26, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix bug where the timestamp's microseconds value is greater than 999999
3 participants
@bsiegel @huguesv @bndw