Autocomplete: __minikube_handle_flag:29: bad math expression: operand expected at end of string

[RobbeVW]

What Happened?

After installing autocomplete for ZSH, autocompletion throws __minikube_handle_flag:29: bad math expression: operand expected at end of string

	$ minikube completion zsh > ~/.minikube-completion  # for zsh users
	$ source ~/.minikube-completion

.zshrc

autoload -Uz compinit
compinit

# Load Angular CLI autocompletion.
source <(ng completion script)

# Minikube
source <(minikube completion zsh)  # This ensures Minikube completion is sourced
source <(kubectl completion zsh)

alias kubectl="minikube kubectl --"
alias k="minikube kubectl --"

# The next line updates PATH for the Google Cloud SDK.
if [ -f '/Users/robbe.vanwortswinkel/Documents/google-cloud-sdk 2/path.zsh.inc' ]; then . '/Users/robbe.vanwortswinkel/Documents/google-cloud-sdk 2/path.zsh.inc'; fi

# The next line enables shell command completion for gcloud.
if [ -f '/Users/robbe.vanwortswinkel/Documents/google-cloud-sdk 2/completion.zsh.inc' ]; then . '/Users/robbe.vanwortswinkel/Documents/google-cloud-sdk 2/completion.zsh.inc'; fi

Attach the log file

log.txt

Operating System

macOS (Default)

Driver

Docker

[wgzhao]

I met the same error

• OS: Ubuntu 24.04
• minikube: v1.33.1
• Driver: docker-ce 27.1.2
• ZSH: 5.2.21

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Ritikaa96]

This kind of error occur in Mac due to extra tab /indentation too, there can be other reasons as well.
such as zsh setup was not done correctly , try exec zsh or source ./zshrc

• If this is because zsh trying to indicate insecure repositories, try
  compaudit | xargs chmod g-w to

[Ritikaa96]

/kind support

[Ritikaa96]

if the issue is resolved , you can close it using /close
in case it persists , please show the output of compaudit

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten