Node errors reach the editor as flattened strings instead of structured NodeError
Maintainers usually reply within 1 day
@shhlife is already working on this.
Since Oct 7, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem
This library's nodes fail with plain exceptions, so their errors reach the editor as one flattened string. Messages often repeat the node's name (f"{self.name}: …") or print a provider response into the text, and the editor has to parse them back apart.
griptape-ai/griptape-nodes-engine#5738 added NodeError (griptape_nodes.exe_types.core_types) and a structured error field on NodeErrorEvent. Nodes that raise it can send their own message plus labelled fields, the provider's response and links, which the editor shows directly.
What's needed
- Raise
NodeErrorwhere a node fails on a provider or user-fixable problem, or a clear plain exception otherwise. - Drop the
"{node_name}: "prefix from error messages; the engine already sends the node name. - Move provider responses and IDs (generation ID, request ID) out of the message text into
response/fields. - Raise the library's minimum engine version once a stable engine release includes
NodeError(v0.103.2, the latest stable, does not).
Origin
Reported by Jason Schleifer, as part of moving every Griptape node library to NodeError.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from griptape-ai/griptape-nodes-library-diffusers
-
add the ability for the offset sliders to be negative for the latent composite nodePossibly taken @shhlife claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
griptape-ai/griptape-nodes-library-diffusers#126 · 2 assignees ·
Maintainers usually reply within 1 day
-
Latents Composite Mask: only one source latent per node, so multi-element composites need a chain of nodesPossibly taken @ladipobaruwa-fn claimed this 3 days ago. Open
griptape-ai/griptape-nodes-library-diffusers#121 · 1 assignee ·
Maintainers usually reply within 1 day
-
Latents Composite Mask: source latent can't be resized, only placed at its own size or stretched to fillPossibly taken @ladipobaruwa-fn claimed this 3 days ago. Open
griptape-ai/griptape-nodes-library-diffusers#120 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
griptape-ai/griptape-nodes-library-diffusers#115 ·
Maintainers usually reply within 1 day
-
Diffusers library nodes still show the Labs labelPossibly taken @griptapeops claimed this 17 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 30/100
griptape-ai/griptape-nodes-library-diffusers#98 ·
Maintainers usually reply within 1 day
All issues in griptape-ai/griptape-nodes-library-diffusers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SpikeInterface/spikeinterface#4924 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-per-model-bedrock#782 ·
Maintainers usually reply within 1 day
-
bug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
No-op PreToolUse:Bash hook (bash_hook.py) still registered synchronously; adds latency and can time out at 10 sPossibly taken @alexgr-agent claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
alexgreensh/token-optimizer#313 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100