The plugin smooth-checkout checkout hook exited with status 1

[kevawnw]

I am having this error from dockers in bulidkite because of the smooth-checkout-plugin. Can you guys fix this or assist me in how to get pass this.

(Checking out repository)

[2022-11-28T20:17:27Z] 0

  | [2022-11-28T20:17:27Z] :::: local clone location = '.'   | [2022-11-28T20:17:27Z] :::: checkout ref = '88cae23eb4a74df81d2704d28769509e4ca3e93a'   | [2022-11-28T20:17:27Z] :::: git remote url = 'git@github.com:Vydia/web.git'   | [2022-11-28T20:17:27Z] :::: ssh key path = ''   | [2022-11-28T20:17:27Z] :::: clone flags = '--depth 1'   | [2022-11-28T20:17:27Z] Git repository already exists.   | [2022-11-28T20:17:27Z] So, doing a git clean and setting the remote URL   | [2022-11-28T20:17:27Z]   | [2022-11-28T20:17:27Z] We trust you have received the usual lecture from the local System   | [2022-11-28T20:17:27Z] Administrator. It usually boils down to these three things:   | [2022-11-28T20:17:27Z]   | [2022-11-28T20:17:27Z] #1) Respect the privacy of others.   | [2022-11-28T20:17:27Z] #2) Think before you type.   | [2022-11-28T20:17:27Z] #3) With great power comes great responsibility.   | [2022-11-28T20:17:27Z]   | [2022-11-28T20:22:27Z] [sudo] password for buildkite-agent:   | [2022-11-28T20:22:27Z] sudo: timed out reading password   | [2022-11-28T20:22:27Z] 1   | [2022-11-28T20:22:27Z] 🚨 Error: The plugin smooth-checkout checkout hook exited with status 1

[scriptnull]

Hi, thanks for reporting this. It seems to be because the scripts in this plugin assume that a passwordless sudo is possible at certain places.

In order to fix this, we should probably introduce a config option called assume_sudo.

• if set to true , we can make the scripts to use sudo
• if set to false , we will need to avoid calling sudo
• if not set, we will default to some-command || sudo some-command

Feel free to open a pull request if you would like.

[mogopz]

Just chiming in to say I'm also seeing this error - I forked the repo to remove sudo and it's running fine.

Is it there because of something specific to Hasura's setup? I don't believe the default git clean behaviour Buildkite does uses sudo but I might be wrong..