<?xml version='1.0' encoding='utf-8' ?>

<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>Tales of a Fourth Grade Nothing</title>
  <link>https://sawyl.dreamwidth.org/</link>
  <description>Tales of a Fourth Grade Nothing - Dreamwidth Studios</description>
  <lastBuildDate>Tue, 10 Oct 2017 19:49:13 GMT</lastBuildDate>
  <generator>LiveJournal / Dreamwidth Studios</generator>
  <lj:journal>sawyl</lj:journal>
  <lj:journaltype>personal</lj:journaltype>
  <image>
    <url>https://v2.dreamwidth.org/11422004/3139309</url>
    <title>Tales of a Fourth Grade Nothing</title>
    <link>https://sawyl.dreamwidth.org/</link>
    <width>99</width>
    <height>100</height>
  </image>

<item>
  <guid isPermaLink='true'>https://sawyl.dreamwidth.org/1169325.html</guid>
  <pubDate>Tue, 10 Oct 2017 19:49:13 GMT</pubDate>
  <title>Fast turnaround of fixes...</title>
  <link>https://sawyl.dreamwidth.org/1169325.html</link>
  <description>&lt;span style=&quot;font-size: x-large&quot;&gt;S&lt;/span&gt;&lt;span style=&quot;font-variant: small-caps&quot;&gt;uccessful morning working&lt;/span&gt; to debug a series of problems that we&apos;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&apos;t provide any further details.  Within seconds, they&apos;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=&quot;https://www.dreamwidth.org/tools/commentcount?user=sawyl&amp;ditemid=1169325&quot; width=&quot;30&quot; height=&quot;12&quot; alt=&quot;comment count unavailable&quot; style=&quot;vertical-align: middle;&quot;/&gt; comments</description>
  <comments>https://sawyl.dreamwidth.org/1169325.html</comments>
  <category>hacking</category>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
</channel>
</rss>
