Fix deterministic issue when getting pipeline dtype and device #10696
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?
This PR aims to fix a deterministic issue when getting the pipeline dtype or device across multiple runs of the same Python script.
Internally, the ordering issue comes from the use of
set
in the_get_signature_keys
function in thesrc/diffusers/pipelines/pipeline_utils.py
file. As stated in the Python documentation,set
does not guarantee that the elements will have the same order across multiple runs of a Python script. This is due to the hashing algorithm which is initialized with a random salt each time the python interpreter is started. More information can be found here (especially in the second note at the end of the section).Fixes #10671.
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@sayakpaul