same config - GUI works well, cli version breaks

[abcnorio]

Environment

chainner = v0.24.1 from release page (zip, not deb)
OS = debian trixie
GPU = nvidia 4090

Behaviour

• config runs perfectly fine in GUI
• config does not run with chainner run [config] - see attached log

Previously done

• saved config in GUI
• replaced paths with sed under linux on the terminal

Expected behavior

• it should run, because only paths were changed and this is essential for scripting the cli version over different models with varying image folders and different text append
• the GUI complains that the config was changed, but runs without any problem - see log that it runs, tried that several times, no break
• the cli version breaks - see log

AGAIN:

• same config (!!!) ie. 100% identical

Additional question

• What is the proper way to change paths in a .chn config for cli scripting on the terminal? This is essential to be able to change paths and it does not touch or change any nodes. Insofar the explanations on the webpage for cli configs do not seem to be relevant. But nevertheless chainner complains about a changed config that only contains changed paths, nothing else.

Thanks!

LOGS

chainneroutput_TEST1-sed3_chainner_model-images-upscale_v1_GP-chainnersaved.zip
GUI-works-in-contrast-to-cli-same-config_chainner_main.zip
chainner_cli-error.zip

[derek-yn-zhang]

I have a similar issue where a workflow runs without issues in the GUI, but breaks when I run it using the CLI.

Environment

chaiNNer = v0.24.1
OS = macOS Sequoia 15.1.1
GPU = Apple M4 Pro

Behavior

Workflow runs without issues in the GUI
Workflow breaks with CLI command using override option -- see attached log

Expected behavior

The CLI command should work the same way as the GUI, and successfully execute the workflow. I examined logs from the GUI runs, and the error that breaks the CLI version is also present there -- it just doesn't seem to matter.

Logs

chainner_cli_error.log
upscale_chain.chn.zip

Thanks for looking into it!