#93 Bug: clicking on a certain node the GUI has crashed.

[Anonymous]

Originally created by: cola3k
Originally owned by: SouravRoy-ETL

What happened

When clicking on a certain node, the GUI turns into a black screen, it seems that the GUI has crashed directly.

Clicking on/moving other nodes did not cause any problems.

Environment

• Duckle version / release tag: V0.5.0
• Windows 11 x64

[Anonymous]

• assigned_to: SouravRoy-ETL

[Anonymous]

Originally posted by: SouravRoy-ETL

@cola3k - Checking this
@vemasabagaco - What do you mean?

[Anonymous]

Originally posted by: cola3k

I have identified a possible cause of the black screen issue. This workflow was generated by Claude, and when I inspected the JSON file, I noticed that the position.y value was set to 0. After changing it to any other number and reopening the GUI, the black screen no longer occurred. The y value is now overwritten by the GUI upon saving.

For reference, here is the node entry from the JSON:

{  
  "id": "n_join",  
  "type": "transform",  
  "position": {  
    "x": 747.62472543543,  
    "y": -36.31785400911774  
  },  
  ...  
}

(Original y was 0; after manual modification, it works.)

[Anonymous]

Originally posted by: SouravRoy-ETL

@cola3k - Okay I will tune the MCP.

[Anonymous]

Originally posted by: cola3k

Actually, I realized that the crash didn’t happen when I hid the properties panel. However, when I showed the properties panel and clicked on this node, it still crashed. I asked CC (Claude) to analyze the root cause:

Crash reason: The object format "multipleKeys": {"Region": "Region"} is incompatible with the GUI properties panel’s key‑value parser. When clicking the node, the properties panel tries to render → parsing fails → black screen crash.

I later replaced this node with a SQL node to accomplish the same task.

So the root cause is still that the workflow node generated by CC contains an invalid configuration item format and lacks validation, which leads to the crash.

Since the JSON file can be freely edited externally, it would also be best if the GUI could avoid crashing when loading configurations that do not conform to the expected rules.

[Anonymous]

Originally posted by: SouravRoy-ETL

Seems interesting. I will take a look.