-
Notifications
You must be signed in to change notification settings - Fork 816
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
make sure we don't warn on empty tokens #1554
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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'll trust you that this is the correct behaviour, not too versed on this topic 😅
#[cfg(feature = "http")] | ||
#[test] | ||
fn test_from_pretrained() { | ||
fmt() | ||
.with_max_level(tracing::Level::DEBUG) | ||
.with_target(false) | ||
.init(); | ||
let _ = Tokenizer::from_pretrained("Qwen/Qwen2-7B-Instruct", None); | ||
warn!("This should be the first warning"); | ||
} |
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.
What is the purpose of this test?
Will fix clippy on main and merge! |
* make sure we don't warn on empty tokens * Testing the log is actually hard 😓 * mpty
When activating warnings, there was an issue with added tokens that are not part of the vocab. I am pretty sure that the main point about added tokens is that they don't have to be in the vocab, so fixing this.