Port-forward called from Taskfile exit itself

[JeffreyDallas]

Describe the bug

I just did a debug session with Pranali, she is trying to write gitbook documentation for solo.
One thing we found is that is using task to deploy solo, some port-forward would mysteriously exit itself without any errors/logs/warning.
This is the same thing I found when adding a github test flow for Task last December.
In summay, if calling kubectl port-forward within task file, sometimes kubectl port-forward
would quit itself, sometimes is haproxy-node1-svc , one sometimes is hedera-explorer one.
The workaround I used in github workflow is to re-calling port-forward outside taskfile.

Describe the expected behavior

Port-forward should keep running

To Reproduce

run task default-with-mirror

Additional Context

No response

[JeffreyDallas]

1.Tried with adding "nohup" to detach the process.
2.increase verbose level to 9, not seeing any useful in output or logs
3. use task key word async: true

On macbook, no longer has port-forward exiting issue, but with github runner environment,
it still happens randomly

[JeffreyDallas]

Further experiment showed that with macOS, if direct logs to a regular file, port-forward invoked from Taskfile with "nohup" can consistently run successfully.
But if direct logs to /dev/null , port-forward invoked from Taskfile with "nohup" sometimes still exit itself.

[JeffreyDallas]

Tried "nc -vz 127.0.0.1 ", first attempt is successful, then port-forward quitted, the second attempt failed