<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dw="https://www.dreamwidth.org">
  <id>tag:dreamwidth.org,2017-04-18:3139309</id>
  <title>Tales of a Fourth Grade Nothing</title>
  <subtitle>sawyl</subtitle>
  <author>
    <name>sawyl</name>
  </author>
  <link rel="alternate" type="text/html" href="https://sawyl.dreamwidth.org/"/>
  <link rel="self" type="text/xml" href="https://sawyl.dreamwidth.org/data/atom"/>
  <updated>2017-10-10T19:49:13Z</updated>
  <dw:journal username="sawyl" type="personal"/>
  <entry>
    <id>tag:dreamwidth.org,2017-04-18:3139309:1169325</id>
    <link rel="alternate" type="text/html" href="https://sawyl.dreamwidth.org/1169325.html"/>
    <link rel="self" type="text/xml" href="https://sawyl.dreamwidth.org/data/atom/?itemid=1169325"/>
    <title>Fast turnaround of fixes...</title>
    <published>2017-10-10T19:49:13Z</published>
    <updated>2017-10-10T19:49:13Z</updated>
    <category term="hacking"/>
    <dw:security>public</dw:security>
    <dw:reply-count>0</dw:reply-count>
    <content type="html">&lt;span style="font-size: x-large"&gt;S&lt;/span&gt;&lt;span style="font-variant: small-caps"&gt;uccessful morning working&lt;/span&gt; to debug a series of problems that we've been working on for at least the last three years.  Every time we run a test, we get slightly closer to a solution; but every time we try, uncover yet another glitch, making our approach to a solution somewhat asymptotic.&lt;br /&gt;&lt;br /&gt;After carefully enabling debugging &amp;mdash; something which, when switched on across the board, generates so much data that it causes everything to grind to a halt in a matter of minutes &amp;mdash; and tracing a job, I noticed that the start of the job coincided with a periodic cleanup event.  Checking the source code, I noticed the cleanup was using a negative match to determine what to remove, confirming my suspicion that either a race condition or a type mismatch was to blame.&lt;br /&gt;&lt;br /&gt;The person I was working with was in a chat session with the developer.  They mentioned that we thought the failure was caused by a race with the periodic event but didn't provide any further details.  Within seconds, they'd got a reply which effectively restated our hypothesis.  Then, a few seconds after that, they got another message from the developer saying that they were in the process of producing a fix and could we please send the logs for confirmation.&lt;br /&gt;&lt;br /&gt;It took longer to work out how to transfer the logs than it took to develop a first cut fix for the problem...&lt;br /&gt;&lt;br /&gt;&lt;img src="https://www.dreamwidth.org/tools/commentcount?user=sawyl&amp;ditemid=1169325" width="30" height="12" alt="comment count unavailable" style="vertical-align: middle;"/&gt; comments</content>
  </entry>
</feed>
