<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Rust on Brownian Motion</title>
		<link>https://www.davidb.org/tags/rust/</link>
		<description>Recent content in Rust on Brownian Motion</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 29 Jul 2026 10:59:19 -0600</lastBuildDate>
		
			<atom:link href="https://www.davidb.org/tags/rust/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A Latent Upstream Bug, Found and Fixed in About 30 Minutes</title>
				<link>https://www.davidb.org/post/2026/latent-upstream-bug/</link>
				<pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.davidb.org/post/2026/latent-upstream-bug/</guid>
				<description>&lt;p&gt;&lt;em&gt;I keep seeing arguments about AI coding assistants conducted entirely in the abstract, so here is a concrete one: a real change I made recently, start to finish, including the parts that went wrong. Everything below is a real MCUboot change; the PR numbers are live and you can check my work.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;An automated review of an external contributor&amp;rsquo;s pull request flagged that the author had quietly disabled a test on one simulated device. Rather than stopping at &amp;ldquo;you disabled a test&amp;rdquo;, the model worked out &lt;em&gt;why&lt;/em&gt; the test failed — a long-standing bug in MCUboot&amp;rsquo;s own test simulator that had been invisible for as long as it had existed, and only became observable because this PR raised a configuration limit. The fix was implemented, reviewed, pushed as &lt;a href=&#34;https://github.com/mcu-tools/mcuboot/pull/2808&#34;&gt;PR #2808&lt;/a&gt;, and then empirically demonstrated to resolve the original author&amp;rsquo;s problem.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Cost: roughly 30 minutes of my attention, some of it spent doing other things while test suites ran. My honest estimate for doing this by hand is one to two days&lt;/strong&gt; — most of it spent staring at trailer arithmetic trying to work out why an &amp;ldquo;oversized&amp;rdquo; image wasn&amp;rsquo;t oversized.&lt;/p&gt;&#xA;&lt;p&gt;The tool was Claude Code running Opus 5.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
