Feature request: better (any) debugging
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
I think I speak for many when I say discords, YTs, reddit and - everything really - are FLOODED with people with zero coding skills (not a criticism, just an observation) who have no clue what to do when comfy throws. See, the thing is for non-coders a big red message is like a BSOD - they don't understand comfy is fine - they think the whole thing is 'broken' and I lost count of other none coders telling them to 'wipe and reinstall' - sometimes the entire OS - i kid you [not](https://www.reddit.com/r/comfyui/comments/1b3n5yr/nodes_caused_memory_loop/).
Content creators and discords shouldn't have to debug things for others - yet they do because we are the nicest community ever :) Please consider adding a better exception mechanism. For example, upon throwing because an input is receiving an incorrect data type, it would be easy to do a catch that would pick up what error type it is, and provide suggestions to fix it.
So yeah, better debbuging would be great, and for those of us that can code, a step by step debugger with a step in/ step out and variable monitoring would be great. We can't just stick beautify on the back of every node and check datatypes each time : )
Thank you for considering this and making the best software since sliced bread! 👍 💯
Contributor guide
Assessment
This issue has not been assessed yet.