πΎ bltroutwine π @bltroutwine@social.tchncs.de
It's amazing what we've built without really knowing how to do it well at all.
Go to None branch where I haven't what to do yet verbiage:
I really would like to upgrade cernan to toml 0.3 but the API has changed juuuust enough that updating https://github.com/postmates/cernan/blob/master/src/config.rs is going to be a massive pain. I also ought to add feature flags to slim down the default build but, again, config.rs makes that a challenge.
Anyone have examples of #rustlang projects that have non-trivial configuration but also haven't entered tire-fire territory?
When testing in stage accidentally turns into testing in production: http://www.airspacemag.com/military-aviation/mind-if-i-borrow-it-76518363/?all
TECH PEOPLE: We have serious concerns that the growth of commercial social media and websites has severe privacy implications for everyone.
TECH PUNDITS: I absolutely LOVE this app that automatically broadcasts my location to everyone within a 10 mile radius in the background. It's the best.
a LEGO paper aeroplane making machine https://mastodon.social/media/tYQg2xSwCqWkwJeUejs
Ended up with a very tidy quickcheck test for tailing a file across rotates: https://github.com/postmates/cernan/blob/7ef24e8ad78b23e1fd5fe41a83de709121af816c/src/source/file.rs#L336
The idea here is that we randomly generate actions against a log file β writes, rotations, deletions etc etc βΒ and then assert that the FileWatcher reads all the appropriate lines from the underlying file, which we keep track of in-model. Not bad for slightly less than 100 lines of code.
It's interesting time in randomized testing land, in short.
Part of the challenge of writing effective QC code is that you might well be testing the same path over and over again. Coverage directed fuzzing corrects this excepting that it's focused explicitly on finding crashes, not making assertions.
"Does not crash" is a property though, if you look at it. Why not add more?
"Beginner's Luck: A Language for Random Generators" addresses the problem with base QC in a different way, exposing distribution as a first class concern.
The Prometheus work in cernan came along nicely over the weekend. PR for that work is here: https://github.com/postmates/cernan/pull/242
Of special interest is the Quickcheck model work around the special purpose Prometheus aggregation. I can now say that cernan meets the strict reporting requirements with regard to timestamp / time-series uniqueness.
Doing work in #rustlang QC suggests to me that car-crashing quickcheck and cargo-fuzz would be a valuable avenue of research.
I love to read stories like this about Apollo history. Lunar orbit rendezvous⦠what happens if your command module pilot dies?
spaceflightblunders.wordpress.com/2017/04/07/lunβ¦
@randomgeek Got a good chuckle out of your avatar when the notification popped up!
βοΈ
Oooh I have been forgetting the rear thread guide!
Boy howdy, if someone tells you that learning to sew again after a decade and change away from any of it will come right back, uh, well, they're probably more talented with sewing than I ever was. All I've managed to do today is waste a bunch of thread and bird-nest my machine.
Mathematical Tools for Computer-Generated Ornamental Patterns: https://infoscience.epfl.ch/record/99827/files/mtfco.pdf
https://awoo.space/media/F9TgSVVhIKeTC9wWL7s https://awoo.space/media/FDW6CglH52P7--RGOII https://awoo.space/media/ODQcDTSlkCW0fDNurbg
The one thing I wish I could correct about undergrad was my squeamishness toward writing marginalia. It's remarkably useful to carry on a conversation with yourself through the text, time. I wonder now what my thinking was while reading Advanced Programming in the Unix Environment or Automata Theory, Languages, and Computation. Now I know these things but then it was new and strange. There's value in that ignorance I've been cut off from.
Oh well!
Drink coffee all morning and read ShΕ«saku EndΕ's Silence? Don't mind if I do, hail storm, don't mind if I do.
Come the afternoon I imagine I'll be writing quickcheck code. This'll do until then, that's for sure.
A Mastodon instance where the CoC specifies everyone roleplays a Mind from a spacecraft in the Culture series https://en.wikipedia.org/wiki/List_of_spacecraft_in_the_Culture_series
At the same time as we're focused on lolspeed cernan also has to maintain accuracy of implementation. That means quickcheck and fuzzing. I'd like to get integration level fuzzing going Real Soon Now. All that work reduces the unknowns to a tiny, contained, subset of the system. It's a good time.
Effectively, cernan ought to deal with the machine as found and saturate it. Meanwhile cernan must not be overwhelmed itself or lose accuracy. To that end I built a semi-durable queue https://github.com/postmates/hopper for use in cernan's store and forward internal architecture. We keep accuracy going by the use of CKMS: bounded memory with guaranteed worst case error. It's tidy, I think.
