[Chandler-dev] "skipping recursive refresh"

[Morgen Sagen]

Bryan Stearns gave me a copy of his chandler.log which had the  
following:

2007-03-16 10:12:37,983 repository INFO: <DBRepositoryView:  
viewpool-0 (5)> committed 2 items (1 kbytes) in 0:00:00.047000, 43  
items/s (21 kbytes/s)
2007-03-16 10:12:38,155 repository WARNING: <DBRepositoryView:  
MainThread (2)> skipping recursive refresh
2007-03-16 10:12:38,467 stderr WARNING: Traceback (most recent call  
last):
2007-03-16 10:12:38,467 stderr WARNING:   File "z:\bugfix\chandler 
\application\Application.py", line 1058, in OnMainThreadCallbackEvent
2007-03-16 10:12:38,483 stderr WARNING:     event.target(*event.args,  
**event.kwds)
2007-03-16 10:12:38,483 stderr WARNING:   File "z:\bugfix\chandler 
\util\task.py", line 86, in mainCallback
2007-03-16 10:12:38,483 stderr WARNING:     f(x)
2007-03-16 10:12:38,483 stderr WARNING:   File "z:\bugfix\chandler 
\application\dialogs\SubscribeCollection.py", line 259, in success
2007-03-16 10:12:38,483 stderr WARNING:     self._finishedShare(result)
2007-03-16 10:12:38,500 stderr WARNING:   File "z:\bugfix\chandler 
\application\dialogs\SubscribeCollection.py", line 138, in  
_finishedShare
2007-03-16 10:12:38,500 stderr WARNING:     collection = self.view[uuid]
2007-03-16 10:12:38,500 stderr WARNING: KeyError: <UUID:  
b47fe714-7366-11db-e188-dc3aea7c16a9>

Just prior to this, the log shows normal subscribe activity, and my  
guess is that the commit( ) shown is from line 104 of /util/task.py  
-- this is on the repository view used to subscribe, and the purpose  
of it is to make all the sharing view changes available to other  
views.  Once that has completed, wx.GetApp().PostAsyncEvent( ) is  
used to let the main thread know it's time to refresh the main  
repository view (line 136 of /application/dialogs/ 
SubscribeCollection.py).  However, this refresh doesn't seem to  
happen, as indicated by the "skipping recursive refresh" message  
above, and the subsequent failure to find the subscribe collection in  
the main repository view.

Any ideas how we're getting a "recursive refresh"?  Does the  
PostAsyncEvent( ) call "interrupt" what's going on in the main  
thread?  (I'm assuming it doesn't)

Thanks,
~morgen