ComfyUI Node Runs on cloud

Stringify

See what's actually flowing through a wire

By ali1234·Created 3 years ago·Updated 3 months ago· 130
Stringify
  • x
  • str
  • repr

Sometimes you don't need a clever debugging tool, you just need to know what's on a wire. Stringify is exactly that: plug anything into it and it hands you back a plain-text version of the value, so you can actually read it instead of guessing.

How it works

There's no cleverness here and that's the point. The node accepts any type at all - its input socket is a wildcard, so it'll connect to an IMAGE, a MODEL, a STRING, one of this pack's own SEQUENCE or JOB values, whatever you've got. It then calls Python's str() and repr() on whatever came in and returns both as separate STRING outputs. str() is the "readable" version; repr() is closer to what you'd type to reconstruct the value, and for simple things like numbers, plain strings, and lists of dictionaries (which is exactly what a JOB is under the hood) the two usually look almost identical. Where it earns its keep is on values you can't otherwise inspect on the graph at all - a SEQUENCE, a JOB, a value pulled out by GetAttribute - since ComfyUI's UI won't show you the contents of a custom type on its own.

The inputs and outputs that matter

  • x (*, any type) - the only input. Wire literally anything into it.
  • str (STRING, output) - Python's str() of the input.
  • repr (STRING, output) - Python's repr() of the input.

That's the whole node. It's not an output node itself, so it doesn't display anything by default - you still need to route one of its STRING outputs into something that shows text on screen (a text-preview node, a Save Text, whatever your setup already has) to actually see the result.

How to install it

Via ComfyUI Manager: search "comfyui-job-iterator", install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/ali1234/comfyui-job-iterator

Restart ComfyUI. No dependencies, nothing to download - this whole pack installs in seconds, which is a genuine relief given how often a single custom node install turns into a Python dependency fight in this ecosystem.

Common issues & troubleshooting

You wired it up and "nothing happens." That's expected - Stringify only produces two STRING outputs, it doesn't display them anywhere itself. Connect the str or repr output into a text-display node to actually read the result.

You're trying to debug a GetAttribute value and it comes back looking wrong. Wire GetAttribute's output straight into Stringify before you send it anywhere else in your workflow - it's the fastest way to confirm you're pulling the value (and the type) you think you are, especially when chasing a mismatched name between MakeJob and GetAttribute.

str and repr look identical and you expected a difference. For plain values - numbers, short strings, lists, dicts (which is what this pack's JOB and ATTRIBUTES types actually are) - Python's str() and repr() often do produce the same output. The distinction matters more for objects with custom string formatting; if you're not seeing a difference, that's not a bug, it just means the value you're inspecting doesn't have one.

Categoryali1234/debug

Inputs (1)

NameTypeDefaultDescription
x*

Outputs (2)

NameTypeDescription
strSTRING
reprSTRING