Pipeline specs invalid after running a pipeline

[FGRCL]

Summary:

After running a pipeline, the pipeline specs get modified into an invalid format. The parameters blocks have both a parameters and container key for their action.

Expected behavior:

The parameter blocks should only have a parameters action.

Actual behavior:

The parameter block has a parameters and container action.

Steps to reproduce:

1. Drop a new pipeline with parameters
2. Execute the pipeline
3. Save the pipeline to a directory
4. Open the pipeline.json file
5. Notice the action for the parameter blocks

Zetaforge version:

main

Operating System

Other (specify)

Other operating system:

all

Logs:

"file-6wt21sinahw9": {
      "information": {
        "id": "file",
        "name": "File",
        "description": "File parameter input.",
        "system_versions": [
          "0.1"
        ],
        "block_version": "block version number",
        "block_source": "core/blocks",
        "block_type": "compute"
      },
      "inputs": {},
      "outputs": {
        "path": {
          "type": "file",
          "connections": [
            {
              "block": "canny-edge-k2o7j05im846",
              "variable": "image_path"
            }
          ]
        }
      },
      "action": {
        "container": {
          "image": "",
          "version": "",
          "command_line": []
        },
        "parameters": {
          "path": {
            "value": "pipeline-y67j70mliceo/0190cb52-cd75-7b56-a3d1-82d45a437dbe/DBP distribution.png",
            "type": "blob"
          }
        }
      },
      "views": {
        "node": {
          "active": "True or False",
          "title_bar": {},
          "preview": {},
          "html": "<input type='file' name='fileInput' parameters-file/>",
          "pos_x": "795",
          "pos_y": "224",
          "pos_z": "999, this is the z-index for 2D canvas",
          "order": {
            "input": [],
            "output": [
              "path"
            ]
          }
        }
      },
      "events": {}
    },

Recording:

No response

Anything else?:

No response