Félix Saparelli
Félix Saparelli
This will be in 1.21.1
Default has now changed, but a bit more cleverly than I suggested here: - if the `SHELL` environment variable is set, we use that - if we detect we're running...
1. go from watchexec instead. sounds like you've already found the docs for that 2. yes, signal handling. you'll want to handle signals on one instance only 3. if you're...
Are you using the latest watchexec patch? There's a regression introduced by recent Rust that manifests like this, and it was fixed in latest.
Just not going to do this, it's too out of scope. The new modes from `--emit-events-to` may help writing helpers for this; otherwise this is something that should go to...
~~Second this, it's weird and annoying that whenever the operator pod gets restarted, it changes name to `{hostname}-1`. Combined with #10102 it means a proxy-on operator is very fragile, a...
Yeah, I was about to edit. I'm filing [a new issue](https://github.com/tailscale/tailscale/issues/11156) and reading the logfile for any necessary redaction noticed it was trying (and failing, due to the issue) to...
We've had our own gh action for a while now. Closing.
The OP request is now possible with `--map-signal INT:INT`.
This was since fixed, sometime about 1.22.1.