You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello (foo={{{ echo bar }}} | bar={{{ echo foo }}});
I compile with complgen aot --bash-script hello.bash hello.usage.
When compiling multiple times I see at least three different contents for hello.bash, e.g. the function _hello_cmd_0 gets renamed to _hello_cmd_1 and vice versa. So far I saw this only happening when the usage file contains multiple external command outputs.
Functionally all behave the same, but is there a way the aop command deterministic/idempontent, so that the same usage-file always produces the same bash-script?
I want to run complgen in a build pipeline on every commit. And a reproducible build pipeline should always create the same content, when the source (here usage file) hasn't changed.
The text was updated successfully, but these errors were encountered:
Hi. Take a look at the latest master branch. I don't see the _hello_cmd_X names variability anymore. There may be additional sources of non-determinism left that should also be fixable.
I have the following
hello.usage
:I compile with
complgen aot --bash-script hello.bash hello.usage
.When compiling multiple times I see at least three different contents for
hello.bash
, e.g. the function_hello_cmd_0
gets renamed to_hello_cmd_1
and vice versa. So far I saw this only happening when the usage file contains multiple external command outputs.Functionally all behave the same, but is there a way the
aop
command deterministic/idempontent, so that the same usage-file always produces the same bash-script?I want to run
complgen
in a build pipeline on every commit. And a reproducible build pipeline should always create the same content, when the source (here usage file) hasn't changed.The text was updated successfully, but these errors were encountered: