Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to suppress warning "Ignored unknown kwarg option direction"
See original GitHub issueHi
I am using the default example code with sentence-transformer version 2.1.0 and I get the following warning each time I use model.encode
>>> embeddings = model.encode(sentences)
Ignored unknown kwarg option direction
This is very annoying when I’m trying to use this in a loop with tqdm. Is there a way to remove this warning?
Thanks
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How does one ignore unexpected keyword arguments passed ...
The most important thing you can do with the second that you can't do with the first is take a as a positional...
Read more >mBART-model7 part 1 orig - Kaggle
WARNING : Running pip as the 'root' user can result in broken permissions and ... unknown kwarg option direction Ignored unknown kwarg option...
Read more >ignore transformers warning - Code Examples & Solutions For ...
ignore transformers warning ; 1. import transformers ; 2. transformers.logging.set_verbosity_error() ; 3. .
Read more >mpl_toolkits.mplot3d.axes3d. - Matplotlib
The axis direction for the zs. This is useful when plotting 2D data on a 3D Axes. The data must be passed as...
Read more >Migrating to SQLAlchemy 2.0
The use of *args and **kwargs has been removed both to remove the complexity of guessing what kind of arguments were passed to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the same issue. It is an issue in tokenizers. Updating to the newest version helped:
Have tried with the updated version of tokenizers (0.11.6), but still see this warning multiple times while using keyBERT.
However, I see this warning while I run this in a notebook, but not in the shell.