Task fails when using "time" in the cmd

[SethCurry]

I have a Taskfile that's failing to run, despite that it most likely should. It looks like this:

build: cmds: - time go build -i

Which causes it to throw this error:

task: Failed to run task "build": 1:1: unhandled command node: *syntax.TimeClause

It looks like mvdan/sh is intercepting "time", assuming it's the shell keyword, and expecting something to happen with that.

A short workaround if anyone else needs it is to change time go build -i to $(which time) go build -i. It will change you from using the shell keyword time to the system's time binary, which is much uglier, but it gets the job done.

[andreynering]

/cc @mvdan

[mvdan]

Yes - in Bash, time is a builtin and parses differently. For example, time foo | bar times all of foo | bar, while /bin/time foo | bar times just foo.

It's an unfortunate regression because earlier versions of the parser didn't do this correctly, so the interpreter just executed the system's time. Now we should add support for the keyword in the interpreter.

Another, easier workaround is to do "time" go build ..., as quoting the string means it can't be a keyword.

[andreynering]

FIxed on master and new release by updating the upstream library.

Thanks @mvdan