Andrew Lilley Brinker
Andrew Lilley Brinker
Hi everyone! I'd signed myself up previously to rework the site, and I think my thoughts have coalesced that I am starting to put a real plan together. ## Information...
Right now we have some out of date version numbers in the README. Ideally `cargo release` would bump those automatically when we release new versions.
Currently, Hipcheck uses the `salsa` crate to provide "incremental computation," meaning the ability to write code which recognizes when some value has already been computed, and to reuse that computation...
`cargo-dist` automatically generates a self-updater, and it would be nice if we could leverage it, if present, to allow an easy path for users to self-update Hipcheck. The basic idea...
`clap`, which we use to define our CLI interface, has two mechanisms you can use for that definition. Currently, we use the runtime mechanism, but it would be better if...
Hipcheck requires some files to be present / findable by it in order to run. Currently, these are checked at the start of running Hipcheck, but it checks them one...
Right now you can configure Hipcheck to produce scores based on weights for different analyses, but you can't really see the calculated percentages for each leaf of the scoring tree,...
Can coordinate with @Amndeep7. We have a `Containerfile` but don't currently push any prebuilt images to Dockerhub. Ideally we'd do this with each new version in an automated fashion. The...
Hipcheck is slow to build today, and we can and must do better. This general goal of "drive down build times" impacts many things we care about in the Hipcheck...
While we'd like Hipcheck to be robust and minimize crashing, we should also be realistic and recognize that Hipcheck _will_ sometimes crash and we ought to do our best to...