-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Bump com.azure:azure-storage-blob from 12.28.1 to 12.29.1 in /plugins/repository-azure #17562
Bump com.azure:azure-storage-blob from 12.28.1 to 12.29.1 in /plugins/repository-azure #17562
Conversation
Bumps [com.azure:azure-storage-blob](https://github.com/Azure/azure-sdk-for-java) from 12.28.1 to 12.29.1. - [Release notes](https://github.com/Azure/azure-sdk-for-java/releases) - [Commits](Azure/azure-sdk-for-java@azure-storage-blob_12.28.1...azure-storage-blob_12.29.1) --- updated-dependencies: - dependency-name: com.azure:azure-storage-blob dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
❌ Gradle check result for 1707bac: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 1707bac: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@chengwushi-netapp Can you investigate this test failure please? At first glance it appears to be a different exception type than asserted, possibly as a result of the version bump. |
Looks like the relevant change here: Azure/azure-sdk-for-java#42149 There was a workaround for a missing upstream dependency static method that was removed. The removed code included a So likely changing the exception type here will fix the bug. |
❌ Gradle check result for 568cbe4: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
568cbe4
to
3704264
Compare
❌ Gradle check result for 3704264: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Daniel Widdis <widdis@gmail.com>
3704264
to
9ec8181
Compare
❌ Gradle check result for 9ec8181: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❕ Gradle check result for 9ec8181: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17562 +/- ##
=========================================
Coverage 72.43% 72.43%
- Complexity 65721 65746 +25
=========================================
Files 5311 5311
Lines 304941 304937 -4
Branches 44228 44226 -2
=========================================
Hits 220890 220890
- Misses 65952 65971 +19
+ Partials 18099 18076 -23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…om.azure-azure-storage-blob-12.29.1 Signed-off-by: Daniel Widdis <widdis@gmail.com>
❌ Gradle check result for 34e5b12: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 34e5b12: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❕ Gradle check result for 34e5b12: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-17562-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2ee86601c9f674862cabf85c7c17aafc4732ffd8
# Push it to GitHub
git push --set-upstream origin backport/backport-17562-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x Then, create a pull request where the |
Bumps com.azure:azure-storage-blob from 12.28.1 to 12.29.1.
Release notes
Sourced from com.azure:azure-storage-blob's releases.
Commits
65ef6d0
Merge remote-tracking branch 'origin/release/patch/20250303' into release/pat...6ae8681
Communication readme updates14c7999
Prepare patch release 20250303 (#44474)09c3a79
Prepare for communication and storage patch releasesf925e94
PR to update the golden samples test to only run on migrated samples (#44471)b540583
Increment versions for remoterendering release (#44454)0fc259c
CircuitBreaker: Partition availability staleness check background thread shou...6cfa56d
use Type instead of class (#44466)a4c0a31
Increment package versions for resourcemanager releases (#44451)c535db2
Update azure-sdk-build-tools Repository Resource Refs in Yaml files (#44458)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)