run-command Crashing; Clue? None ASCII Characters injected into output

[bendhouseart]

Okay, this one has been head scratcher for some time. This CI started failing some time ago and initially I thought that I had messed up the paths of the test files. However, I spent a considerable amount of time running the same matlab commands locally as well as pouring over the locations of test files in the CI.

I'm yet to be able to track things down, but I do sometimes notice non-ASCII characters appearing in the output of the runner:

  No such file or directory:
  /home/runner/work/PET2BIDS/PET2BIDS/ecat_validation/synthetic_ecat_integer_16x16x16x4.v.gz
  failed to convert:Invalid file identifier. Use fopen to generate a valid file
  identifier.Ø failed to convert:$� failed to convert:A

I'm not sure if it's related, but I'm hoping that there's some strange locality or other setting that is messing up my paths within my runner.

Willing to try and submit a PR or keep hacking away on my end to try and diagnosis this if you're able to view/review.

Thanks

[mcafaro]

@bendhouseart This doesn't look like an error that would be related to matlab-actions/run-command in particular. You might consider trying to print out more information about the state of the file or directory when this issue occurs to further debug.

Side note: You might also consider upgrading to V2 of setup-matlab and run-command. V1 was deprecated.