No, I don't think so. I did a clean install locally last week and I only have the RSS-pull action set up. It's a ghost in the machine somewhere ;-) I spent some time tracing through actor messaging paths and I guess I'll just need to spend a little more time on it.
An alternative would be to find an SVN check-in that doesn't have the issue and then track down the exact change that caused the problem. Not sure which will be more difficult ... Ethan On Mon, Oct 18, 2010 at 5:51 PM, Richard Hirsch <[email protected]>wrote: > On Mon, Oct 18, 2010 at 5:41 PM, Ethan Jewett <[email protected]> wrote: > > Hi all, > > > > Dick did some testing after my commits today and found a couple of > issues. > > The first (ESME-290) was that I broke the public timeline. That is now > > fixed. > > > > The second issue is ESME-291 - > > https://issues.apache.org/jira/browse/ESME-291. The problem is that > replies > > show up duplicated in the streams view and in the public timeline view > > (though in the public timeline view it is *only* for messages that were > > created before the public timeline actor started up, so if you create new > > replies you need to restart the server to see them duplicated in the > public > > timeline). This is actually an old issue. It exists at least in release > 1.1 > > and probably well before that. > > > > The reason this is happening is that when a reply is created there are > > actually two messages created and persisted to the database. One is > created > > in the UserActor, which is what is supposed to happen. But another > message > > is created somewhere else and I can't figure out where! Any ideas? > > Some action maybe? > > Maybe Vassil has an idea. > > > > Ethan > > >
