xd009642

There’s a saying of designing things so you fall into the pit-of-success.

In the previous sections we’ve designed and implemented a websocket service that takes a stream of audio, resamples it and runs a hypothetical machine learning model on it either working on voiced segments or the entire stream.

I’ve been inspired to write something for April Cools Club, and what fits better from my normal content than my experience rice farming in rural Japan!

Given a Rust project using workspaces with potentially a large amount of packages how can we make it quicker to run tests or other tooling when the project changes.

I did one last year so it’s probably time for another year in review.

Recently I’ve been doing tackling some issues in my open source projects related to Ferrous System’s work to get code coverage for libcore - the Rust core library.

For those who aren’t aware, Trustfall is a pretty cool tool.

You might want to read the previous post.

This week I’ve dropped two cargo-tarpaulin releases, both of which have significant speed-ups for LLVM coverage reporting.

This is an announcement blogpost for wiremocket a wiremock influenced library for mocking websocket servers.

All the code can be found on this branch if you look at main you’ll see future post content there!

This post is going to go through my process of PRing something to the fake crate.

I feel like I’ve managed to do quite a lot this year and also have a lot planned.

This entry will lean a lot on types from streaming API design feel free to refer back if any of the types are unexpected.

In the last entry, it was decided that the audio coming in would be PCM data with a specified sample rate, channel count, and data type.

Sometimes, you may end up in a situation where you have a big project to test in CI.

This is part of a series on creating a streaming audio service in Rust, with services such as live transcription in mind.

This is the start of a series about implementing bidirectional audio streaming APIs.

While working on speech/language technology for other languages sometimes I come across linguistic diversions which are endlessly fascinating.

In this post, I’m mainly going to explain a bit about what snapshot testing is some pros and cons and how I approached it for an audio processing project at work.

On Coverage and Macros As a maintainer of a code coverage tool one of the common issues I get is that the coverage statistics are incorrect.

This is a rehosting of a blog originally on www.rs-online.com where our team won a £1,500 prize for the below project.

Tarpaulin (or cargo-tarpaulin) is a code coverage tool for Rust, and anyone who’s used it might know that until recently it had an issue with code that used futures.

Tarpaulin (or cargo-tarpaulin) is a code coverage tool for Rust.

Code coverage When people talk about code coverage, they’re referring to metrics which show how much of their source code is “covered” by their tests.

Well here is the obligatory hello world post.