AssistantV2 API - time incorrectly resolved when timezone is provided about python-sdk

[dorringel]

Hey, We were not able to resolve the issue. Would appreciate the investigation. Thanks

…

On Mon, Jun 14, 2021, 19:30 Angelo Paparazzi ***@***.***> wrote: @dorringel <https://github.com/dorringel> Thank you for submitting this issue and my apologizes for the late response time. In this time, have you managed to resolve the issue? If not, I will perform an investigation this week to try to replicate this issue and work on potential solutions. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#784 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRLWVLT4ZLDZICF7JGVSCLTSYVEDANCNFSM4245OEOA> .

[apaparazzi0329]

@dorringel Thank you for submitting this issue and my apologizes for the late response time. In this time, have you managed to resolve the issue? If not, I will perform an investigation this week to try to replicate this issue and work on potential solutions.

[apaparazzi0329]

I have a pretty good feeling this issue is related to time differences from daylight savings given that there is only a one hour difference. This does not appear to be a python-sdk issue but I am asking around to see if this a common issue or a possible service bug. I will update you here but feel free to experiment with this knowledge if you haven't already. For instance, changing EST to EDT.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.