Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Serverless changing DateTimeOffset value timezones
See original GitHub issueDescribe the bug
When sending messages from a Functions backend to SignalR serverless, which contain DateTimeOffset timestamps, the messages are arriving at the Client having had their Offset changed.
(Am seeing the +8 hr timezone, which is not a timezone that any of my Function or App Services are running in)
To Reproduce
Send a message to SignalR serverless which contains a DateTimeOffset value which has, for example, no Offset so is UTC. Observe that the client receives the message with the Offset changed to a different Timezone.
This occurs whether sending the message via Azure Function Output Bindings, or using the Management SDK.
Logging the value of the DateTimeOffset before sending shows that it has the correct Timezone/Offset.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@oatsoda The fix has been applied to all the regions.
@andrew-tevent The code to fix the issue in the service side is merged, but it will take about two months to be released. I will keep you updated in the future.