While testing the code on the provided example, I encountered an issue at the YALTAi step. I noticed that at this stage, the outputs are written in JSON format but saved in XML files.
This inconsistency between the file content and extension caused issues in the workflow (not running the rest of the process).
I resolved the problem by adding the --alto option to the Yaltai command. After this modification, everything works as expected but I think it's weird that I had to do that...
Is this behavior normal or intended?
Could this be due to a recent change in Yaltai or Kraken?
Environment
Yaltai version on yaltaienv: 2.0.4
Kraken version on krakenv: 5.2.9
Hi !
While testing the code on the provided example, I encountered an issue at the YALTAi step. I noticed that at this stage, the outputs are written in JSON format but saved in XML files.
This inconsistency between the file content and extension caused issues in the workflow (not running the rest of the process).
I resolved the problem by adding the
--alto
option to the Yaltai command. After this modification, everything works as expected but I think it's weird that I had to do that...Is this behavior normal or intended? Could this be due to a recent change in Yaltai or Kraken?
Environment
Yaltai version on yaltaienv: 2.0.4 Kraken version on krakenv: 5.2.9