-
Notifications
You must be signed in to change notification settings - Fork 850
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.
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
[AzDatalake] APIView Feedback + Samples + Doc + CI/Live issues cleanup #21348
Merged
tasherif-msft
merged 96 commits into
Azure:feature/azdatalake
from
tasherif-msft:final-cleanup
Aug 16, 2023
Merged
[AzDatalake] APIView Feedback + Samples + Doc + CI/Live issues cleanup #21348
tasherif-msft
merged 96 commits into
Azure:feature/azdatalake
from
tasherif-msft:final-cleanup
Aug 16, 2023
+3,778
−1,466
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Enabled gocritic's evalOrder to catch dependencies on undefined behavior on return statements. Updated to latest version of golangci-lint. Fixed issue in azblob flagged by latest linter.
* Adding header and value * Wiring and tests * format * Fixing value * change log
…e#20710) Logging improvements: * Updating the logging to print more tracing information (per-link) in prep for the bigger release coming up. * Trimming out some of the verbose logging, seeing if I can get it a bit more reasonable. Stress tests: * Add a timestamp to the log name we generate and also default to append, not overwrite. * Use 0.5 cores, 0.5GB as our baseline. Some pods use more and I'll tune them more later.
Co-authored-by: Scott Beddall <[email protected]>
…re#20721) This now works just like the message batch - you'll get an ErrMessageTooLarge if you attempt to send a message that's too large for the link's configured size. NOTE: there's a patch to `internal/go-amqp/Sender.go` to match what's in go-amqp's main so it returns a programmatically useful error when the message is too large. Fixes Azure#20647
…re#20722) When the remote entity is full we get a resource-limit-exceeded condition. This isn't something we should keep retrying on and it's best to just abort and let the user know immediately, rather than hoping it might eventually clear out. This affected both Event Hubs and Service Bus. Fixes Azure#20647
* Update changelog with latest features Prepare for upcoming release. * bump minor version
Co-authored-by: scbedd <[email protected]>
The checkpoint store wasn't guarding against multiple owners claiming for the first time - fixing this by using IfNoneMatch Fixes Azure#20717
…zure#20437) * [Release] sdk/resourcemanager/paloaltonetworksngfw/armpanngfw/0.1.0 generation from spec commit: 85fb4ac6f8bfefd179e6c2632976a154b5c9ff04 * client factory * fix * fix * update
* add sdk/resourcemanager/postgresql/armpostgresql live test * update assets.json * set subscriptionId default value * format
* add sdk/resourcemanager/eventhub/armeventhub live test * update assets
* add sdk/resourcemanager/compute/armcompute live test * skus filter * fix subscriptionId default value * fix * gofmt * update recording
* sdk/resourcemanager/network/armnetwork live test * update subscriptionId default value * update recording
* add sdk/resourcemanager/cosmos/armcosmos live test * update assets.json * update assets.json * update assets.json * update assets.json
…e#20737) We shouldn't be resetting the etag to nil - it's what we use to enforce a "single winner" when doing ownership claims. The bug here was two-fold: I had bad logic in my previous claim ownership, which I fixed in a previous PR, but we need to reflect that same constraint properly in our in-memory checkpoint store for these tests.
Co-authored-by: James Suplizio <[email protected]>
…e latest message) (Azure#20744)
…ocesing (Azure#20751) Co-authored-by: James Suplizio <[email protected]>
* Fixing connection string parse logic * Update README
* fix flaky test * charles suggestion
Co-authored-by: Wes Haggard <[email protected]>
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
3 similar comments
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azdatalake - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
gapra-msft
approved these changes
Aug 16, 2023
tasherif-msft
changed the title
[AzDatalake] APIView Feedback + Samples + Doc
[AzDatalake] APIView Feedback + Samples + Doc + CI/Live issues cleanup
Aug 16, 2023
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.