| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Thanks Google.
|
| |/ |
|
| |
|
|
| |
This wasn't used anywhere, and never gets hit. It's a neat hack, but not worth the cognitive and maintenance cost of keeping around.
|
| | |
|
| |\
| |
| | |
Actix 4 and askama (as a way of fixing vulns detected by dependabot).
|
| | |
| |
| |
| | |
This was obviated by upgrading past Actix 3.
|
| | |
| |
| |
| |
| |
| | |
The author of maud seems to be slow on updating to newer actix releases, and the syntax, while clever, is ultimately less tool-friendly than "HTML with some weird characters" is.
I do still like the idea, but I also want to use Actix 4.
|
| | |
| |
| |
| | |
`maud`, which was the main reason for nightlies, relies on proc macros. Those are stable in the 2021 edition, and maud 0.23+ uses them in a stable-friendly way.
|
| |/
|
|
|
|
| |
This is in preparation for a bulk update - Github notified me that there are a ton of outdated deps here (which is true), so I'm using this as an opportunity to practice handling stale deps.
Part of the motivation here is for `cargo upgrade` (from `cargo-edit`) to be able to do something reasonable.
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Package updates
|
| | |
| |
| |
| | |
This is more of a speculative update than a response to any specific issue, but I'd rather do this intermittently than have to upgrade in a hurry if a dep gets breached.
|
| | |
| |
| |
| | |
The maintainer has put up-to-date packages on crates.io, so let's use 'em for hygiene.
|
| |\ \
| | |
| | | |
Update Rust nightly version
|
| |/ / |
|
| |\ \
| |/
|/| |
Update Rust nightly version
|
| |/ |
|
| |\
| |
| | |
Automate periodic Rust Nightly upgrades.
|
| | |
| |
| |
| | |
Now that it's done in two (well, three, if you count the README) places, it's best if its done consistently.
|
| | |
| |
| |
| | |
This allows the project to have a pinned version of Rust, but also ensures we don't fall too far behind on versions so long as someone (cough) reviews the pull requests regularly. This splits the difference between using nightly directly (and having Travis fail sporadically because of missing rustfmt/clippy) and pinning so that Travis works reliably (and having a large version lag).
|
| |\ \
| |/
|/| |
Add an admonishment to check the version you're testing against.
|
| |/
|
|
| |
@wlonkly!)
|
| |\
| |
| | |
Pin nightly again.
|
| |/
|
|
| |
As predicted in 6b271b72d91ece90325b7d1691759d1c2b25707f, nightly-as-of-today is missing tools this project depends on (rustfmt, again).
|
| |\
| |
| | |
Switch from quickcheck to proptest.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The argument is as given in the proptest docs at
<https://altsysrq.github.io/proptest-book/proptest/vs-quickcheck.html>.
I've found that the resulting tests are somewhat clearer, and that the
tools for working with test case generation are more useful.
The other killer feature is recalling test failure examples from run to
run. This change includes at least one bug found while testing the port!
Finally, if <https://github.com/AltSysrq/proptest/issues/179> is to be
believed, proptest is considerably closer to supporting async tests.
|
