fix: bump github.com/Azure/azure-kusto-go from 0.5.0 to 0.60 and make timing more granular #10966
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.
Required for all PRs:
Version 0.6.0 of the go SDK, among other irrelevant changes, updates its azure blob library to a version that doesn't leak memory and solves upload failures.
Additionally, when serializing the timestamp to kusto, the granularity was increased from a second to a nanosecond, and the format is now hardcoded to be
time.RFC3339Nano
, which kusto accepts.