_.isTraceback

The most honest thing I can tell you about _.isTraceback is that you will probably never use it. It checks whether the object on its input is a Python TracebackType - the object Python builds to carry exception stack information when something throws. That is not a thing that normally travels over a Comfy wire.

Why it exists

The ovum/underscore family in sfinktah/comfy-ovum is generated wholesale: the pack walks every method on underscore3, a Python port of Underscore.js, and creates a node per method. The port has an unusually complete set of type guards - isSlice, isFrame, isModule, isTraceback and friends - so the generator dutifully exposes all of them. You get the full collection whether or not anyone asked for it. That's the whole story.

How it works

The test is type(obj) is TracebackType. One optional input, obj (type *), accepts anything you throw at it. One output, typed * (ANY), which at runtime is a Python bool - not one of the nodes the generator stamped with a proper BOOLEAN type, so a strict boolean socket may need a cast. And like every node in the family, if you feed it a _.CHAIN from _.chain, it returns a chain so you can keep the pipeline moving and pull the value out at the end with _.value.

The one realistic scenario

If you're building something genuinely unusual - a workflow where a custom node or an LLM node catches an exception and passes the traceback object onward for inspection - _.isTraceback is your guard before you try to render or inspect it. You could branch on it: if it's a traceback, stringify the exception info; if not, pass the value through. That's a legitimate, if vanishingly rare, edge case. For everyone else, this node is a conversation piece.

Installing comfy-ovum

ComfyUI Manager: search for comfy-ovum, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sfinktah/comfy-ovum
pip install -r comfy-ovum/requirements.txt

Restart and you're set. No model downloads, no CUDA - it's a pure-Python utility pack with a few small dependencies. Just remember the author's own note on the family: work in progress, not recommended for production workflows. In this node's case that's about the only way to describe it, because it's hard to imagine a production workflow that needs a traceback type check at all.