Error logging on Github Actions

Quality of life issue, within the GitHub actions logs when yargs fails to parse an option it doesn’t seem to want to display which argument it failed to parse.

Locally there is no issue:

~/projects/cml$ ./bin/cml.js runner --fail-arg 
cml.js runner

Launch and register a self-hosted runner

Options:
...

Unknown arguments: fail-arg, failArg

However, when this happens on an internal project it does not print the argument as expected:

I tried and failed to simply reproduce a similar outcome But on an internal project, this is consistently reproducible…

I’m not sure if this is a strange error with the GitHub runner environment or something that has to do with the logger is printing/being passed through?

https://github.com/iterative/cml/blob/4508871d60811210481482bc461fcdc245e52c92/bin/cml.js#L10-L26

and here

https://github.com/yargs/yargs/blob/59a86fb83cfeb8533c6dd446c73cf4166cc455f2/lib/usage.ts#L40-L75

If you can spell correctly this isn’t an issue…😉 so I’d consider this a very low priority if one at all and --cloud-startup-scrip is indeed not an argument 😞

[casperdcl]

upstream issue https://github.com/yargs/yargs/issues/2033

[dacbd]

I agree on this is not something that should be resolved in CML, I initially thought there was something strange going on with how the logging was being done.