h4 - Debug Error (TEST ONLY)

H4_DebugErrorGenerator is a test instrument, not a workflow tool - the display name says it all: "Debug Error (TEST ONLY)". Its entire job is to throw errors on purpose so you can verify that ComfyUI's error popup (which h4 calls the "Death Modal") actually works: that it appears, that log sanitization is working, that the GitHub search links function, and that the full-report window opens. If you're a workflow user, you almost certainly don't need this node. If you're developing custom nodes, tweaking h4's error reporting, or debugging why a workflow fails in a specific way, it's a convenient way to produce a controlled, reproducible crash instead of praying a real one happens.

It's deliberately buried. The source comments note it's only meant to be visible when debug mode is enabled in settings, and it lives in the h4/debug category - not somewhere you'd stumble into by accident. That's the right call for a node whose entire purpose is to break things.

The settings

• error_type - none (passthrough, no crash), or minor (a ValueError), warning (a RuntimeError), critical (presumably the loudest path). You pick the flavor of failure you want to observe.
• trigger - the safety switch. The error only fires when this is true. Set it false again after testing, or you'll keep crashing every run.

The output

One status string. With trigger off it reports something like "Debug Error Generator: Standby. Set trigger=True to test." With trigger on and error_type set to none, it tells you no error is selected. Pick a real error type with the trigger on, and the node raises - the string never makes it out because the exception fires first.

How to install

It's part of h4_Live, so: ComfyUI Manager → search "h4_Live", or:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live

restart. No dependencies. If you can't see the node in the menu, that's expected - check your debug-mode setting, which is exactly the setting this node exists to test.

Where people get burned

The obvious one: forgetting to flip trigger back to false and then wondering why a workflow that "should work" keeps dying. The node is honest about it in its own tooltip - "Set back to FALSE after testing" - and it's worth taking that literally. Second: don't mistake this for a useful thing to keep on a real canvas. It's a lab tool. If you're not actively testing error reporting, it has no business in a production workflow. And if your goal is actually debugging a real failure, the README's honest guidance applies here too: h4's enhanced error popup can feel "jarring" the first time it fires - that's a feature, not a bug in your setup.