VaeImageProcessor.blur() docstring is missing blur_factor and has a copy-pasted description
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Open src/diffusers/image_processor.py and read VaeImageProcessor.blur() alongside nearby docstrings. Update the Args and Returns/description text to document blur_factor and accurately describe blurring, keeping the existing style and length. Done when the single-file docstring matches the method’s behavior and nearby documentation conventions.
Written by the indexing model from the issue text.
Description
VaeImageProcessor.blur()'s docstring is missing the blur_factor parameter entirely, and its
Returns/description text appears to be copy-pasted from a different method — it currently
describes converting an image to grayscale, not blurring it.
Location: src/diffusers/image_processor.py, VaeImageProcessor.blur(), around line 271.
Proposed fix: add the missing blur_factor entry to the Args section and correct the
description to accurately describe the blur behavior, matching the style of nearby docstrings
in the same file (1-3 sentences, no more).
I have a small, single-file fix ready and would like to open a PR for this if a maintainer can
confirm it's welcome — happy to follow whatever review process you prefer.
- Dominant language
- Python
- Stars
- 34.6k
- Forks
- 7.4k
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 48
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from huggingface/diffusers
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
huggingface/diffusers#14888 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
huggingface/diffusers#14881 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
huggingface/diffusers#14864 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
huggingface/diffusers#14837 ·
Maintainers usually reply within 1 day
-
bug needs-env-info pipelines
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
huggingface/diffusers#14794 ·
Maintainers usually reply within 1 day
All issues in huggingface/diffusers
Similar issues
-
Improve Task Cache Windows Registry events to carry the task subkey's last written time and key pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
log2timeline/plaso#5299 · 1 comment ·
Maintainers usually reply within 2 days
-
deployment release-lag
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nolte/kamerplanter#2047 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClanGenOfficial/clangen#6216 · 1 comment ·
Maintainers usually reply within 1 day
-
API bug connectors
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyinfra-dev/pyinfra#1986 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
521xueweihan/HelloGitHub#3847 ·