-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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
add return_tensor parameter for feature extraction #19257
add return_tensor parameter for feature extraction #19257
Conversation
The documentation is not available anymore as the PR was closed or merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All up for it.
This PR needs to add some kind of test to make sure this argument works
Ideally in tests/pipelines/test_pipelines_feature_extraction.py::run_pipeline_test
that way we make sure it works for all pipeline that are supposed to work.
b426b78
to
a0677bf
Compare
Feedback has been addressed :) |
Not sure what's happening with CircleCI... |
Last suggestion was addressed, but CircleCI Pipeline still seems broken... |
@ajsanjoaquin do you have circleCI set up on your account/branch ? I remember people sometimes having issues because of this. Otherwise, could you try to rebase on Pinging @LysandreJik that might know more. |
The CircleCI pipeline seems to be working again! |
fa74148
to
771b975
Compare
For quality can you try
? |
@Narsil when running
|
What OS/Linux flavor you're running on ? Shell maybe ? |
I'm in a temporary dev environment, so I'm using Windows 😅. I'll use WSL next time. So the formatting error was simply a result of missing newline before importing torch and tf? |
We use |
@Narsil can this PR be merged soon when it passes all tests? I just resolved a conflict made by a different commit on the same file. |
@ajsanjoaquin |
0184e44
to
2ab8d05
Compare
@Narsil the
I hope this can be passed soon before another PR like #19382 modifies the exact code I was working on... |
add return_tensor parameter for feature extraction Revert "Merge branch 'feature-extraction-return-tensor' of https://github.com/ajsanjoaquin/transformers into feature-extraction-return-tensor" This reverts commit d559da7, reversing changes made to bbef892.
Co-authored-by: Nicolas Patry <patry.nicolas@protonmail.com>
2ab8d05
to
da1c7be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I took the liberty of rebasing and fixing your PR. Is the result OK for you ?
@sgugger for final review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this! Just one nit on the docstring.
Co-authored-by: Sylvain Gugger <35901082+sgugger@users.noreply.github.com>
This PR was based on an old fork of the repo and as such, the pipeline tests were not run. They do not pass, so I will revert the commit. Could you open a new PR with fixed tests? |
I am confused, should we re-open a PR or start from here #19679 (I tried re-opening a PR but it resulted in a no-op...) |
* add return_tensors parameter for feature_extraction w/ test add return_tensor parameter for feature extraction Revert "Merge branch 'feature-extraction-return-tensor' of https://github.com/ajsanjoaquin/transformers into feature-extraction-return-tensor" This reverts commit d559da7, reversing changes made to bbef892. * call parameter directly Co-authored-by: Nicolas Patry <patry.nicolas@protonmail.com> * Fixup. * Update src/transformers/pipelines/feature_extraction.py Co-authored-by: Sylvain Gugger <35901082+sgugger@users.noreply.github.com> Co-authored-by: Nicolas Patry <patry.nicolas@protonmail.com> Co-authored-by: Sylvain Gugger <35901082+sgugger@users.noreply.github.com>
…ce#19257)" (huggingface#19680) This reverts commit 35bd089.
What does this PR do?
Fixes #10016
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Addresses stale issue #10016. Please review @LysandreJik and @Narsil. Thanks.