Skip to content
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

Investigate persistent unknown kwargs log message #24

Open
parkerduckworth opened this issue Mar 7, 2022 · 6 comments
Open

Investigate persistent unknown kwargs log message #24

parkerduckworth opened this issue Mar 7, 2022 · 6 comments

Comments

@parkerduckworth
Copy link
Member

During vectorization, the message Ignored unknown kwarg option direction is repeatedly logged, seemingly once per vector created.

Investigate this issue, and see if it can be resolved.


Example screenshot:

Screen Shot 2022-03-07 at 4 21 06 PM

@parkerduckworth
Copy link
Member Author

Found a related issue in the huggingface transformers repo. Some users reported that upgrading their tokenizers dependency to ~ v0.11.5 helped clear up this problem. This project relies on tokenizers==0.10.3

However, others reported that they had to downgrade their transformers dependency to v4.15.0 to fix it. This project relies on transformers==4.16.2, so I'm not sure if we want to do the same.

@antas-marcin any thoughts?

@nzaw96
Copy link

nzaw96 commented Mar 29, 2022

@parkerduckworth How do I upgrade my tokenizer or transformer?

@parkerduckworth
Copy link
Member Author

@nzaw96 for a specific version you would need to use pip/pip3 and specify the target version. For example:

pip3 install tokenizers==0.11.5 

If just wanting the latest release:

pip3 install tokenizers

You would likely want to update your requirements.txt as well to match the new version(s), if you have one.

@chris-aeviator
Copy link

Does this have any real consequences? I realized inconsistent ingests (ingest works fine, Get queries return only few results from many) and also see this message.

@etiennedi
Copy link
Member

The current assumption is that this has no real consequences.

@byronvoorbach
Copy link
Member

@parkerduckworth @etiennedi Every post to /vectors/ results in this warning getting logged. Are we planning to upgrade to a new transformers version any time soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants