Skip to content

Conversation

@comphead
Copy link
Contributor

Which issue does this PR close?

  • Closes #.

Rationale for this change

cargo-machete identifies an unused dependency and this blocks a bunch of dependabot updates PRs
#18580

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added functions Changes to functions implementation spark labels Nov 10, 2025
@comphead comphead changed the title chore: Remove unused tokio dependency chore: Remove unused tokio dependency and clippy Nov 10, 2025
@comphead
Copy link
Contributor Author

@Jefffrey @alamb PTAL

@alamb alamb mentioned this pull request Nov 10, 2025
Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @comphead -- this looks great to me

I also reviewed Cargo.lock and it looks to me like a bunch of other dependencies are updated as well (which is good, I just want to highlight it too)

@mbutrovich mbutrovich added this pull request to the merge queue Nov 10, 2025
Merged via the queue into apache:main with commit e406689 Nov 10, 2025
32 checks passed
codetyri0n pushed a commit to codetyri0n/datafusion that referenced this pull request Nov 11, 2025
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->

- Closes #.

## Rationale for this change

`cargo-machete` identifies an unused dependency and this blocks a bunch
of dependabot updates PRs
apache#18580

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

catalog Related to the catalog crate functions Changes to functions implementation spark

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants