I don't know the reason why ucode prints help, but it is different than what other interpreters do (sh, python, node).
I know that you can use - to indicate stdin, but it doesn't solve the problem.
I'm trying to write an Ansible module to configure OpenWRT (way better - python is not installed by default, shell lacks support for modules and all other things mentioned in "reasoning" for introduction of ucode).
How Ansible works is it reads shebang, so if module starts with #!/usr/bin/ucode it will transfer it to the node via ssh and execute.
That "transfer" element is what causes issues. Ansible can execute module in 2 ways: pipelining - when shebang is executed as ssh argument and the body of module is piped to stdin or copying file (when file is copied into temporary folder and executed as a parameter). This is not controlled by the module in question (but rather a global setting / per connection override).
(Actually, Ansible doesn't support interpreter arguments in shebang at all - ansible/ansible#83603 and I was going to file ticket there, but then realized that there is no way to support non-pipelining mode if shebang contains stdin as an argument).
I don't know the reason why ucode prints help, but it is different than what other interpreters do (sh, python, node).
I know that you can use
-to indicate stdin, but it doesn't solve the problem.I'm trying to write an Ansible module to configure OpenWRT (way better - python is not installed by default, shell lacks support for modules and all other things mentioned in "reasoning" for introduction of ucode).
How Ansible works is it reads shebang, so if module starts with
#!/usr/bin/ucodeit will transfer it to the node via ssh and execute.That "transfer" element is what causes issues. Ansible can execute module in 2 ways: pipelining - when shebang is executed as ssh argument and the body of module is piped to stdin or copying file (when file is copied into temporary folder and executed as a parameter). This is not controlled by the module in question (but rather a global setting / per connection override).
(Actually, Ansible doesn't support interpreter arguments in shebang at all - ansible/ansible#83603 and I was going to file ticket there, but then realized that there is no way to support non-pipelining mode if shebang contains stdin as an argument).