I am not a bash expert and find @dawidwys, you are right. To be accurate, it would be `bash -x COMMAND 2>&1 | grep exec` or something, otherwise it prints scare text. >From my side it is a frequent demand to see what the real command executed so >I would approve this change. We could achieve it even just by hacking this >script locally. So the problem is whether we provide such feature within the >project and, well, the print format and the approach by setenv not optimized >so it looks like no more than just `bash -x`
[ Full content available at: https://github.com/apache/flink/pull/6690 ] This message was relayed via gitbox.apache.org for [email protected]
