Feature Request: Add Detailed Error Information for Node-Specific Data Parsing Failures

[LeonRust]

• Dora Version: 0.3.13

When starting a dataflow file, if a node fails to parse the received data due to incorrect data format, the current error message lacks key context to identify which node is causing the issue. As shown in the attached image, the existing error output only indicates a parsing failure but does not specify the problematic node’s name, ID, or related metadata.

This makes it difficult to quickly locate and debug the root cause, especially in complex dataflows with multiple interconnected nodes.

Requested Enhancement

• Include the node identifier (name or ID) in the error message when data format parsing fails.
• Add supplementary details such as the received data snippet (truncated if necessary) or expected data format to assist with debugging.

Having this information would significantly improve debugging efficiency by directly pointing to the problematic node, reducing the time spent on tracing the error source.

[phil-opp]

This error looks like a version mismatch between the CLI and coordinator. Are you sure that the dora coordinator version is also v0.3.13?

Does the same error happen when you use dora run instead of dora start?

[LeonRust]

I can't reproduce it now, but I'll try to see how.

[haixuanTao]

Yeah, I imagine it to be an error when you compiled using the newly merged #1178 on main and other node not being updated leading to a failed serialization

[phil-opp]

Let's close this for now until we're able to reproduce this again.

Just let us know in case it happens again @LeonRust , then we reopen this issue.