Please include .onnx in folder_paths.py
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- python
- Domain
- machine-learning
Research direction
Open folder_paths.py and trace how model extensions are recognized for custom nodes. Compare the expected .onnx lookup with the WanAnimatePreprocess issue linked in the report, then verify that WanAnimatePreprocess can find .onnx models in its folder.
Written by the indexing model from the issue text.
Description
Custom Node Testing
- I have tried disabling custom nodes and the issue persists (see how to disable custom nodes if you need help)
Expected Behavior
WanAnimatePreprocess custom node can find .onnx models in the folder
Actual Behavior
Cannot find .onnx
Steps to Reproduce
install wananimatepreprocess customnode and try to find .onnx
Debug Logs
As shown in this image
https://private-user-images.githubusercontent.com/205815892/597188112-d7f5e812-f9b4-4cb7-a218-817f5bc9ae81.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODI3NTAyMjAsIm5iZiI6MTc4Mjc0OTkyMCwicGF0aCI6Ii8yMDU4MTU4OTIvNTk3MTg4MTEyLWQ3ZjVlODEyLWY5YjQtNGNiNy1hMjE4LTgxN2Y1YmM5YWU4MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNjI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDYyOVQxNjE4NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jMTZlNjcxZDZiMzBjZTc5YjU5YmVlMDZmMjk1OWUwMjIzNjE1NGFkMTkwOWQyNmEzZDEyZDg4OWIwMDdkOWVhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.hJThCkF8y8kGKBUkcvVi42ApeIgYYFzrg8Ej-NfPGOQ
Other
Solution is to just add .onnx as in here
https://github.com/kijai/ComfyUI-WanAnimatePreprocess/issues/33
- Dominant language
- Python
- Stars
- 134k
- Forks
- 15.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 161
Contributor 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 Comfy-Org/ComfyUI
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Potential Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
All issues in Comfy-Org/ComfyUI
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100