All of my LTX 2.3 workflows have this error, "DualCLIPLoader json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)"

Open
  • Is something wrong?
#515 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
machine-learning

Research direction

The traceback passes through execution.py and the comfyui-lora-manager metadata_hook.py, but the JSON file that fails to parse inside DualCLIPLoader is not named, and the workflow was not attached. Start by reproducing with a DualCLIPLoader whose input file is empty or starts with a non-JSON character, then find where that file is opened and parsed. Done would mean the loader reports which file is invalid instead of a bare JSONDecodeError. The reporter has not yet supplied the workflow, so this needs a maintainer's clarification first.

Written by the indexing model from the issue text.

Description

Every one of the same type with a dual clip loader has crashed with a .json returning with a zero, crashing them all...

I've seen some fixed by digging through quite a bit of stuff to find a .json that starts with a weird character.

I am not that tech savvy.....anyone got a real world answer?

json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

ComfyUI Error Report

Error Details

  • Node ID: 334
  • Node Type: DualCLIPLoader
  • Exception Type: json.decoder.JSONDecodeError
  • Exception Message: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Stack Trace

  File "C:\Users\Owner\ComfyUI-Installs\ComfyUI\ComfyUI\execution.py", line 542, in execute
    output_data, output_ui, has_subgraph, has_pending_tasks = await get_output_data(prompt_id, unique_id, obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb, v3_data=v3_data)
                                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\Users\Owner\ComfyUI-Installs\ComfyUI\ComfyUI\execution.py", line 341, in get_output_data
    return_values = await _async_map_node_over_list(prompt_id, unique_id, obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb, v3_data=v3_data)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\Users\Owner\ComfyUI-Installs\ComfyUI\ComfyUI\custom_nodes\comfyui-lora-manager\py\metadata_collector\metadata_hook.py", line 171, in async_map_node_over_list_with_metadata
    results = await original_map_node_over_list(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<2 lines>...
    )
    ^

Attached Workflow

Please make sure that workflow does not contain any sensitive information such as API keys or passwords.

Workflow too large. Please manually upload the workflow from local file system.

Additional Context

(Please add any additional context or steps to reproduce the error here)

Dominant language
Python
Stars
4.2k
Forks
508
Avg merge
7h 14m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Lightricks/ComfyUI-LTXVideo

All issues in Lightricks/ComfyUI-LTXVideo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.