Use -fetch_stdout with erl_call to support printing of unicode

[starbelly]

Per this comment , erl_call is not very unicode aware, but it will print what is returned in unicode if the -fetch_stdout option is utilized.

This may be tested by generating a release, starting it up, and then running an eval against it like so :

$ _build/default/rel/app/bin/app eval 'io:format("~ts~n",[[257]]).'
ā
ok

Inversely, doing this on main as it is will get you :

_build/default/rel/feedhack/bin/feedhack eval 'io:format("~ts~n",[[257]]).'
ok

[tsloughter]

Huh, interesting. Any possible repercussions to enabling fetch_stdout?

[garazdawi]

Any possible repercussions to enabling fetch_stdout?

You get stdout when you don't expect it to be there :D So just as when we changed from nodetool to erl_call we lost things written to stdout, this would now again print those things.

[starbelly]

Oh hmm. If relx is supporting versions prior to 24 then this will need to be made conditional.

[tsloughter]

@garazdawi ah... I guess that is good, but also bad since we told people they weren't getting that, haha.

@starbelly support should just be 28, 27, 26 I think. So Github actions need to be updated.

[starbelly]

@starbelly support should just be 28, 27, 26 I think. So Github actions need to be updated.

Updated. Windows test failing, but that seems unrelated.