Phil Pennock
Phil Pennock
Is there enough interest/use-case for being able to specify `gimme abcdef1234` to get a specific git sha and be able to do so repeatably, using cached builds rather than rebuilding...
We have 50+ TLS keys and certs inside the nats-server codebase, as test-data. Certificates expire and need to be reissued, and requirements change. We need a sane way to manage...
### Proposed change When configured as a leafnode, the nats-server might have NATS credentials configured in it, to connect a local account to a remote account in a system running...
Constrain our server auth nonce selection with a no-op change for the current server code-base, in a way which we guarantee and expect clients to check for, to buy us...
If an HTTP(S) request is received without the Upgrade: header, then if this new option is set then we'll assume it's a browser and issue a redirect. There's no flexibility...
### Observed behavior The Go maintainers have released a new tool, **`deadcode`**: This is a "zero false negatives" (as long as in Go and without linker symbol aliasing) approach, and...
### Observed behavior Given a hostname `example.org`, running: ```sh nats -s tls://example.org server info ``` _succeeds_, but ```sh nats -s tls://example.org/ server info ``` **fails**; if the hostname points to...
The file `.git/config` can be added to and removed from though automation, but does support comments. Using `git bug` in a repo stomps on the file, rewriting it and losing...
**Description** With cosign 2, when verifying a signature in the transparency logs, an OIDC issuer and subject must be matched, but there's very little guidance as to what the options...
(First, thank you for this tool, it's very helpful in double-checking that correct fields have been changed! Made my day.) Given a top-level list, each member of which is an...