[chandler-users] Recurring items disappearing from Calendar view with recent builds

[Aparna Kadakia]

Andre,
Thank you for additional details on this. I will append it to the bug  
report to help developers debug this problem better.

Thanks again...
Aparna


On Jan 25, 2007, at 9:51 PM, Andre Mueninghoff wrote:

> Hi Aparna,
>
> That sounds very similar and could be the same thing. One pattern that
> seems to exist is that if I click on any of the recurring events being
> displayed, all displayed recurring events disappear. If I sync-all,  
> they
> reappear. Another pattern is that if I select an event in the calendar
> view and in the detail view make that event a recurring event,  
> briefly I
> see a duplicate of the event appear behind the event lozenge I had
> selected. Also, the following traceback then appears endlessly on the
> monitor/log (DOS window). I had to kill the python process in Windows.
>
> MemoryError: (12, 'Not enough space')
> Traceback (most recent call last):
>   File "C:\Program
>   Files\Chandler0.7alpha5\parcels\osaf\framework\blocks\Table.p
> y", line 157, in OnPaint
>     wx.GetApp().fireAsynchronousNotifications()
>   File "C:\Program Files\Chandler0.7alpha5\application 
> \Application.py",
>   line 846
> , in fireAsynchronousNotifications
>     view.itsVersion -= 1
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepositoryVi
> ew.py", line 302, in refresh
>     txnStatus = self._startTransaction(False)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepositoryVi
> ew.py", line 162, in _startTransaction
>     return self.store.startTransaction(self, nested)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepository.p
> y", line 1135, in startTransaction
>     locals['txn'] = DBTransaction(self, None, status)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepository.p
> y", line 835, in start
>     return store.repository._env.txn_begin(_txn,  
> DBEnv.DB_TXN_SNAPSHOT)
> MemoryError: (12, 'Not enough space')
> <DBRepositoryView: MainThread (305)> refresh aborted by error
> Traceback (most recent call last):
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepositoryVi
> ew.py", line 302, in refresh
>     txnStatus = self._startTransaction(False)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepositoryVi
> ew.py", line 162, in _startTransaction
>     return self.store.startTransaction(self, nested)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepository.p
> y", line 1135, in startTransaction
>     locals['txn'] = DBTransaction(self, None, status)
>   File "C:\Program
>   Files\Chandler0.7alpha5\repository\persistence\DBRepository.p
> y", line 835, in start
>     return store.repository._env.txn_begin(_txn,  
> DBEnv.DB_TXN_SNAPSHOT)
> MemoryError: (12, 'Not enough space')
> <DBRepositoryView: MainThread (305)> refresh aborted by error
>
> Andre
>
> On Thu, 25 Jan 2007 21:27:42 -0800, "Aparna Kadakia"
> <aparna at osafoundation.org> said:
>> Andre,
>> I have seen similar behaviour today with some recurring events
>> disappearing from my calendar upon sync. This is without even
>> overlaying calendars. I  have subscribed to the Office calendar and
>> when I synced it, I found some of the events missing.
>> I am not sure if this is the same issue you are seeing but here's a
>> bug I filed for it:
>>
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=7900
>>
>> Aparna
>>
>>
>> On Jan 25, 2007, at 9:12 PM, Andre Mueninghoff wrote:
>>
>>> I should clarify my intentions...I don't expect an immediate fix for
>>> this even if others are experiencing the same behavior. My
>>> intention is
>>> to get help to determine whether there is something that should be
>>> investigated further to package up perhaps a bit of feedback (or a
>>> bug)
>>> for the developers. Knowing the recurrence branch recently landed  
>>> and
>>> the dust is still settling, I also just wanted to mention what I'm
>>> seeing. (BTW, the master event / child event(?) behavior of  
>>> recurring
>>> items in the dashboard seems to work quite intuitively with  
>>> regards to
>>> where items jump to in the list as a result of automatic setting of
>>> triage status when an item is made recurring.
>>>
>>> Thanks, Andre
>>>
>>> On Thu, 25 Jan 2007 23:56:15 -0500, "Andre Mueninghoff"
>>> <andre_mueninghoff at fastmail.fm> said:
>>>> Hi, Has anyone else noticed that recurring events flicker/flash  
>>>> for a
>>>> micro-second and then disappear from the Calendar view as one
>>>> switches
>>>> between collections? I have noticed this since this morning
>>>> Eastern time
>>>> with builds r1293X forward. (I should add that I nearly always
>>>> have all
>>>> collections "pinned up" (what I call it), that is, I see all
>>>> events for
>>>> the visible week for all collections at the same time colored
>>>> respectively by collection color.) It seems that after a sync-all,
>>>> indexes are refreshed or something, and all appears  
>>>> correct...until I
>>>> select a user collection. The view seems the most stable and
>>>> consistent
>>>> if I leave the Sharing Activity collection selected (which I do
>>>> not pin
>>>> up). Since this could be a config issue on my part, I decided to
>>>> post it
>>>> here to the users list first to poll for similar experiences or
>>>> guidance.
>>>>
>>>> Thanks, Andre
>>>> -- 
>>>>   Andre Mueninghoff
>>>>   andre_mueninghoff at fastmail.fm
>>>>
>>>> _______________________________________________
>>>> chandler-users mailing list
>>>> chandler-users at osafoundation.org
>>>> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>>> -- 
>>>   Andre Mueninghoff
>>>   andre_mueninghoff at fastmail.fm
>>>
>>> _______________________________________________
>>> chandler-users mailing list
>>> chandler-users at osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>>
> -- 
>   Andre Mueninghoff
>   andre_mueninghoff at fastmail.fm
>