Skip to content

Fix potential resource leak in CloudFetchQueue #1899

Fix potential resource leak in CloudFetchQueue

Fix potential resource leak in CloudFetchQueue #1899

Triggered via pull request July 9, 2025 01:41
Status Failure
Total duration 9s
Artifacts

dco-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error
check
You only have one commit incorrectly signed off! To fix, first ensure you have a local copy of your branch by [checking out the pull request locally via command line](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally). Next, head to your local branch and run: ```bash git commit --amend --no-edit --signoff ``` Now your commits will have your sign off. Next run ```bash git push --force-with-lease origin fix-download-leak ``` Commit sha: [ac4713e](https://github.com/databricks/databricks-sql-python/pull/624/commits/ac4713e8a5f9bd153f2048a9ef3a9d8bafc8bc40), Author: varun-edachali-dbx, Committer: varun-edachali-dbx; The sign-off is missing.