<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>Wow!!  you are super serious about folia!!  Dual monitors, just so you can keep tabs on it?  That's amazing!!  And I thought that I was obsessed with it!! :)</body>
    <created-at type="datetime">2009-10-01T08:27:29-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12873</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-01T08:27:29-07:00</updated-at>
    <user-id type="integer">5779</user-id>
  </post>
  <post>
    <body>Hi graibeard - we'll take a look into this and see what's going on, thanks for logging this :)</body>
    <created-at type="datetime">2009-10-01T15:26:51-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12875</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-01T15:26:51-07:00</updated-at>
    <user-id type="integer">1</user-id>
  </post>
  <post>
    <body>Unfortunately I can't find any logs for the queue system that manages the grapevine (typical). 

I've fixed the logging now and will monitor the queues - can you post in here if it happens again then I can match it with the logs and see what's going wrong.</body>
    <created-at type="datetime">2009-10-03T04:27:15-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12887</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-03T04:27:15-07:00</updated-at>
    <user-id type="integer">2</user-id>
  </post>
  <post>
    <body>No worries, I'll keep an eye out and log it here if I suspect it's happened again. Thanks.</body>
    <created-at type="datetime">2009-10-03T05:16:36-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12888</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-03T05:16:36-07:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>It surprises me that I caught one of these so soon, but the camera never lies - I think? So, with &quot;a picture being worth a thousand words (edit - deleted)&quot; , here it is. 
That's a Flickr link to the various sizes, the largest of which is a 319KB file so download at your peril but it shows the grapevine at 21:49 on the 4th October (as per the digital clock in the top panel of that image - regularly synced with a known timeserver) - my timezone is (GMT+10.00) Melbourne, and while we've only just rolled over into DST, that's my correct time.
The comment in the right hand browser was made and submitted at approx 21:44 and as you can see by the left browser, it hasn't shown up on the grapevine - ignore the thumbs up to the same journal, this comment should have slotted in after _graibeard gave It's alive! journal entry a Thumbs Up!._  Nyakas two comments came through after I posted it.
BTW - the grapevine shows those comments as being _since about 1 hour ago_ when probably no more than 5 minutes had elapsed? It also does that at times, a large jump in approximated time.

While I'm taking screenshot's, and before I go, this is the grapevine activity as of now --  &quot;22:20 (edit - deleted)&quot; If you're checking logs that's how it appears up to that time.
HTHs</body>
    <created-at type="datetime">2009-10-04T04:28:05-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12906</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-17T15:12:28-07:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>Another one. It's early morning here and the head seriously needs coffee but this one shows a discrepancy between _All Activity -&gt; Everything!_  and the _Grapevine_ 
Om has written a journal entry that has not shown up on the Grapevine - _Om wrote Frost iminent_ It is visible under Friends Journals also, just appears to have been dropped from the Grapevine. 
It's 7:20 on the 10th October here, 20 minutes after the screenshot and nothing has changed on the Grapevine display since the &quot;screenshot was taken (edit - deleted)&quot; - Update, this post has just registered on the Grapevine, still no sign of Om's post though.</body>
    <created-at type="datetime">2009-10-09T13:23:32-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13009</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-17T15:13:12-07:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>That _is_ weird!!  Hey, I just realized that the time difference between us is 16 hours!!  You are 16 hours ahead of us.  I think that is the biggest time difference that I have encountered so far.  I suppose that China has th biggest time diff, or is that a fallacy?  Just me rambling again. :)</body>
    <created-at type="datetime">2009-10-09T14:37:57-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13012</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-09T14:37:57-07:00</updated-at>
    <user-id type="integer">5779</user-id>
  </post>
  <post>
    <body>@graibeard It does look like the grapevine is not logging the odd new entry. Essentially the grapevine is a cut down version of the activity log for performance reasons (the current 100 entries of the 400 000 we have in the Activity Log). I think it's not syncing properly for these cases -  thanks for the screen shots, it really helped to visualise the problem.

</body>
    <created-at type="datetime">2009-10-10T02:16:30-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13017</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-10T02:16:30-07:00</updated-at>
    <user-id type="integer">2</user-id>
  </post>
  <post>
    <body>Given a choice between performance and updates I'll pick performance anyday, but it is nice to see what is going on outside our immediate neighbourhood. Subscribed Groups and Buddies are well taken care of but the gossip around the water-cooler is often worth it for the few gems it delivers, even though it might be a distraction and a waste of the bosses resources. ;)

Is the grapevine a resource hog? Is the auto refresh a burden? I seem to remember you indicating that it was an interim measure that was perhaps getting past its use by date - to paraphrase what I recall.
Personally, I'd be happy for a manual refresh if I could do a query for a predetermined time range or selectable ranges. Perhaps a fixed time limit of say 1 hour or 50 queries. The limit could be extendible to X if it wasn't a resource hog? 
That first page that was returned wouldn't need to be a dynamically generated page either, it could be a static snapshot generated at intervals of say 5 minutes. A timestamp on the generated page would be enough to prove that it was being updated at the server end.  I can certainly live without seeing it scroll over despite what this bug report might imply :-))
Any extensions on that time frame selection would only need to be static pages refreshed hourly and therefore wouldn't necessarily include the first pages (hours) contents (ie:- the latest postings or grapevine equivalent time frame)

Admittedly, the grapevine is useful for catching the odd spammer but the existing tools are fairly good at that.

I assume you're done with the screenshots, if so I'll delete them.
(edit - now deleted from flickr - local copies kept)

</body>
    <created-at type="datetime">2009-10-10T05:17:58-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13018</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-17T15:22:46-07:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>Feel free to delete the screenshot... I have a local copy of it I can use to refer to.

I'm thinking that we don't need the specific grapevine table. When we first made the grapevine we were not running a dedicated database server. You're right it was an interim solution and just needed to find the time and a reason to bring it back up to speed. There's a few other changes we want to make with the grapevine which I'll have incorporated in fixing this issue. Thanks again for helping out with it.</body>
    <created-at type="datetime">2009-10-17T09:56:24-07:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13119</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2727</topic-id>
    <updated-at type="datetime">2009-10-17T09:56:24-07:00</updated-at>
    <user-id type="integer">2</user-id>
  </post>
</posts>
