ferringb

I'd suggest disabling the check if any variable reference is found for those invocations- IE, `use $VAR`. It's a stretch, but consider an eclass that is renaming a use flag-...

I've got no argument w/ the analysis, nor proposal- my original intent was basically what you're suggesting, I just never finished it (and your description is a bit more cogent...

I've updated the PR to use https://pypi.org/project/seed-intersphinx-mapping/ so it automatically tries any pyproject.toml dependencies that have project.url defined. This addresses the DRY aspect.

My general view- and industry view- is input sanitization should be done at the point of deserialization; the underlying pkgcore internal is what's validating this because it's part of the...

A potential compromise here is enhancing the error message to 1) include the repo_id of what was failed to be parsed, and 2) to list the known syncers. It'll still...

Some additional context here: the add/notify pathways were *solely* intended to be used by a repo operation that would be responsible for manipulating the backing store, including the transaction to...

Final comment here- how pkgdev uses `notify_add_package` would require EbuildRepository to rewrite `profiles/categories` to ensure that the packages category is in there. That's likely beyond what you wanted this to...

You want this instead: ``` package main import ( "fmt" "github.com/cloudflare/certmgr/cert" "github.com/cloudflare/cfssl/csr" ) func main() { c := csr.New() x := &cert.Spec{ Request: c, Key: &cert.File{}, Cert: &cert.CertificateFile{}, } fmt.Println(x)...

Just confirming, it's desired that the docs refer to `flyctl` rather than `fly` ? If so, this bit of horribleness (and manual review) does the bulk of it: ``` flyctl...

The cause here is that the code incorrectly assumes that there will only ever be a single user for a given db. So, for example, if you have a sentry...