<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Crash Recovery on TaskFused.com</title>
    <link>https://taskfused.com/tags/crash-recovery/</link>
    <description>Recent content in Crash Recovery on TaskFused.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://taskfused.com/tags/crash-recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How TaskFused Was Tested With Killed Workers and Injected Storage Faults</title>
      <link>https://taskfused.com/how-taskfused-was-tested-with-killed-workers-and-injected-storage-faults/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://taskfused.com/how-taskfused-was-tested-with-killed-workers-and-injected-storage-faults/</guid>
      <description>&lt;p&gt;TaskFused makes one promise above the others: work that two requests share is done once and kept safe, even when the process doing it dies. That&amp;rsquo;s easy to claim and easy to get wrong, so most of the tests try to break it. They kill real processes, make the storage fail on purpose, and drop connections at awkward moments.&lt;/p&gt;&#xA;&lt;p&gt;Every result below comes from the files in &lt;a href=&#34;https://github.com/taskfused/taskfused/tree/main/test/results&#34;&gt;test/results&lt;/a&gt;, recorded from version 0.1.0 on a two-core Linux cloud machine with Go 1.24 and SQLite 3.50.4, with every change flushed to disk. The same tests run on every push, on Linux and macOS.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
