[RFC, Logging] Change warning to info #26545
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
patrickvonplaten
changed the title
LysandreJik
approved these changes
Oct 2, 2023
|
The documentation is not available anymore as the PR was closed or merged. |
blbadger
pushed a commit
to blbadger/transformers
that referenced
this pull request
Nov 8, 2023
[Logging] Change warning to info
EduardoPach
pushed a commit
to EduardoPach/transformers
that referenced
this pull request
Nov 18, 2023
[Logging] Change warning to info
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Change warning to info when adding a new text embedding. The reason is that this warning is trigger every time someone runs:
which confuses users: huggingface/diffusers#5212 .
I don't think we should use
pad_to_multiplehere as it would mean that we add 8 new tokens every time we callload_textual_inversion