Ctrl-C signal not handled if labels not found on forwards about monday

[eko]

Hi @mcadam,

Thank you for reporting this issue, I will try to repoduce in the coming days and will let you know about it. It's great that you have identified a start of the issue :)

[eko]

Hi @mcadam,

Maybe this has been fixed since the 1.0.4 version but here is what I tried to do to reproduce this issue (I've tested with v1.0.8).

I added the following configuration:

# A non-existant label match on Kubernetes
<: &unknown-service-kubernetes
  name: unknown-service
  type: kubernetes
  values:
    context: *kubernetes-context
    namespace: platform
    hostname: unknown.svc.local
    labels:
      app: this-is-totally-unknown-from-kubernetes
    ports:
     - 8080:8080

# A project with this non-existant forward
projects:
 - name: Unknown service (forward)
   forward:
    - *unknown-service-kubernetes

Then, when I run Monday and select this project, I have the following output and when I hit "Ctrl+C", it's OK:

$ monday
✔ Unknown service (forward)

📡  Forwarding 'unknown-service' over kubernetes...
✅  Successfully mapped hostname 'unknown.svc.local' with IP '127.1.2.1' and port 9401
🔌  Proxifying unknown.svc.local locally (127.1.2.1:8080) <-> forwarding to 127.0.0.1:9401
No pod available for selector 'app=this-is-totally-unknown-from-kubernetes': <nil>
👓  Forwarder: lost port-forward connection trying to reconnect...
No pod available for selector 'app=this-is-totally-unknown-from-kubernetes': <nil>
👓  Forwarder: lost port-forward connection trying to reconnect...
No pod available for selector 'app=this-is-totally-unknown-from-kubernetes': <nil>
👓  Forwarder: lost port-forward connection trying to reconnect...
^C
👋  Bye, closing your local applications and remote connections now

I've also tried using the UI with --ui and it's also correctly interrupted

Could you please close this issue if it's fixed for you too?

Thank you

[eko]

Closing this issue as there is no answer and this seems to be fixed now. Thank you.