Replies: 4 comments 4 replies
-
For ancient issues I recommend closing and adding an existing (or new) tag, along with a suggested answer (if you have) when closing. btw, I notice keyword searches on github are impeded. This is probably due to repo being private and back. see if you notice it. Users may be having difficulties searching existing issues. Search "This project needs more collaborators" you won't find it, but you could have before. (maybe it may change search state if someone interacts though) There are such temporary issues like this, I noticed one time it posted my message backwards in the wrong order.. #4331 |
Beta Was this translation helpful? Give feedback.
-
I'd first of all refer people to a few good YouTube guides for proper installation that cover correctly installing prerequisites. |
Beta Was this translation helpful? Give feedback.
-
I support this wholeheartly. Its a pain to see 1.5k issues and so many of them are environment-related ones. |
Beta Was this translation helpful? Give feedback.
-
I think creating more specific categories in the discussions maybe a way to solve this categories like
the idea is to make the issues tab clutter-free as possible if we do make this change, template for issues will be changed to instruct users to post discussions first In addition I also suggest we add categories for
reasons described here #7671 |
Beta Was this translation helpful? Give feedback.
-
Issue page became more of a newsfeed and a way to tell about your suspicious/troubles than clear and concise list of things to fix/implement. So i started to clear it out a bit, and there's a huge amount of issues having the same theme: installation troubles, which often comes down to wrong torch version and/or inability to use GPU. Users that require help should get it, but not at the cost of cluttering issue list, which is important to track actual, verified, reproducable bugs and useful feature requests.
My suggestion: create megathread named something like "Installation Troubleshooting" and pin it, then close all those issues and reroute discussion there, and do so for similar issues in the future. It would be perfectly reasonable to have all those discussions in one place.
I'm sure SOMETIMES the error happens on the repo side, so when there's some reason to believe it or at least a one or two opinions present that issue should be fixed in the repo, then sure, open it and let someone fix it.
If you may suggest any other way of resolving this, please do so.
List of issues i found on the matter, most of them stale and i didnt even touch platform-specific requests like amd gpus or apple silicon.
#352 #704 #733 #759 #783 #829 #1110 #1477 #1493 #1617 #1727 #2152 #2179 #2242 #2450 #2465 #2617 #2786 #3157 #3298 #3779 #3813 #3925 #4061 #4299 #4345 #4346 #4347 #4353 #4412 #4414 #4433 #4447 #4480 #4482 #4677 #4697 #4703 #4949 #4952 #5308 #5485 #6260
14 votes ·
Beta Was this translation helpful? Give feedback.
All reactions