SaltDebugPrint¶
A debug utility node that logs an input value and its type to the application console, then passes the value through unchanged. It supports complex structures (lists, tuples, dicts) and tensors, summarizing tensors by shape.
Usage¶
Use this node inline anywhere you need to inspect the data flowing through a workflow. Insert it between nodes to log intermediate values without altering them. Ideal for verifying shapes, types, or the contents of variables during troubleshooting.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| value | True | WILDCARD | Any value to be logged for debugging. Supports primitives, strings, lists/tuples/dicts (recursively), and tensors. | [1, 2, 3] |
| label | True | STRING | A short label to identify this log entry in the console output. Can be left empty if no label is desired. | encoder_output |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| value | WILDCARD | The original input value, passed through unchanged. | [1, 2, 3] |
Important Notes¶
- Logging format: values are rendered to a concise debug string; tensors appear as Tensor[shape] (e.g., Tensor[1, 3, 256, 256]).
- Collections (lists, tuples, dicts) are logged recursively; very large structures may produce lengthy logs.
- The node uses debug-level logging. If you do not see output, ensure debug logging is enabled for the application.
- Despite the tooltip calling the label optional, the field is required by the node interface. Use an empty string if you prefer no label.
- Sensitive data caution: this node logs values to the console; avoid passing secrets or private data.
Troubleshooting¶
- No log output appears: Ensure the application's log level includes DEBUG and that console logging is enabled.
- Output is too verbose: Reduce collection sizes, pass summaries instead, or avoid logging large objects.
- Only type name is shown for a custom object: The node falls back to the object's class name when it cannot serialize details.
- Unexpected error during logging: The node catches errors internally and still returns the original value; check logs for 'Error in debugtype' or 'Error in debug print' messages.