Félix Saparelli
Félix Saparelli
Along with a `--colo[u]r=always|never|auto` option to control colour handling.
From https://github.com/passcod/cargo-watch/issues/144 Timing of reloading is in question: on command end is a good start, but probably would be even better to watch the various ignore files and reload the...
It would be good and probably solve a few issues to reset the terminal state when the command ends. Specifically thinking of Alternate Screen and Raw Mode. May be what's...
Currently sending signals on windows is not supported. However, there are some "signals" that windows does support: - Ctrl-C (~ SIGINT) - Ctrl-Break (~ SIGTERM) - Ctrl-Close (~ SIGHUP) It...
From https://github.com/watchexec/cargo-watch/issues/178#issuecomment-905519873 Would be a breaking change
When referring to volumes on the CLI, they cannot be addressed using short IDs, like containers and images, only by the full ID: ``` $ hyper volume create dc1ec072da927a2b138702a99a26f22557b53941eae78632aeae9260a0c8d25 $...
I tried to read through the code but I'm not familiar enough with it to understand how this works. I'm looking for a way to _both_ - Make sure the...
For the success payload, the spec says: > `cniVersion` specifies a Semantic Version 2.0 of CNI specification used by the plugin. A plugin may support multiple CNI spec versions (as...
Given the spec versions are semver, semver requirement expressions could be used instead of a static list. Currently a plugin cannot advertise that it supports `1.0.0` and compatible specs with...
For a plugin which supports version 1.0.0 only. The version-command success case is clear: - `CNI_COMMAND=VERSION`, stdin = `{"cniVersion": "1.0.0"}` => plugin exits with code=0, stdout = version payload as...