🤖 Add tests for TokenlessAzureHandler timestamp handling #1069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by Trent Schmidt
Fixes API-5YR
This change introduces a new test suite for the TokenlessAzureHandler's ability to correctly handle timestamps from the Azure DevOps API, focusing on nanosecond and microsecond precision. Three tests were added:
Additionally, changes to azure.py ensure that nanosecond precision timestamps are truncated to six digits when processed, maintaining compatibility with Python's datetime handling.
If you have any questions or feedback for the Sentry team about this fix, please email [email protected] with the Run ID: 2538.