<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dask on Project Wintermute</title><link>https://wintermutecore.com/tags/dask/</link><description>Recent content in Dask on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 17:49:26 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/dask/index.xml" rel="self" type="application/rss+xml"/><item><title>Dask 2026.6.0: Merge Partition Bug and DataFrame Fixes</title><link>https://wintermutecore.com/posts/dask-2026-6-0-release-merge-partition-fix/</link><pubDate>Thu, 11 Jun 2026 17:49:26 +0000</pubDate><guid>https://wintermutecore.com/posts/dask-2026-6-0-release-merge-partition-fix/</guid><description>&lt;p&gt;Dask 2026.6.0 published on 11 June 2026. The headline fix is a &lt;code&gt;DataFrame.merge&lt;/code&gt; regression that silently dropped rows when the graph had exactly 128 or 129 partitions. Operators running wide merges on large partitioned datasets should treat this as a correctness patch, not a cosmetic release.&lt;/p&gt;</description></item></channel></rss>