Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 30427 invoked from network); 18 Oct 2010 15:42:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Oct 2010 15:42:08 -0000 Received: (qmail 93271 invoked by uid 500); 18 Oct 2010 15:42:08 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 93230 invoked by uid 500); 18 Oct 2010 15:42:07 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 93221 invoked by uid 99); 18 Oct 2010 15:42:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 15:42:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vw0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Oct 2010 15:41:59 +0000 Received: by vws3 with SMTP id 3so544688vws.6 for ; Mon, 18 Oct 2010 08:41:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=2REFbGN0jRodGWrhdgcmqzqTEd+FCzf1rFn9kYPez1s=; b=GlQxDQvt/exO9gVEDrkWv0ogHrUHCbyBsrJY96CNlCUBvCnt07z7KSUBPTE0bzaNCX 0DMALBijboyu0cYZ7eLVtT9o+6ohxyswbdtXy71LGomIK0hG3FeFF8tysEOTG4OUjzU/ Z7E64Osghlf5obLOg2ehUxYkrH+ZEc9Jyeh7U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=I8rRiBTecFVbYouR/ytLvDKLwrmEps6R8TIeQd7PIAOH04j1uDyyLqZwSnv7/mu9cu 85TEJmyW6E6AghwKV1v5zinL3l882EDyxXMrtx9oq4QS0MX4mhdoNNG8aHy26x8KTgH6 PmOcgMJ9L4kMqyBvHvSqHshO910BZCvOPX9Gk= MIME-Version: 1.0 Received: by 10.103.6.2 with SMTP id j2mr2565342mui.25.1287416488666; Mon, 18 Oct 2010 08:41:28 -0700 (PDT) Received: by 10.220.181.203 with HTTP; Mon, 18 Oct 2010 08:41:28 -0700 (PDT) Date: Mon, 18 Oct 2010 17:41:28 +0200 Message-ID: Subject: ESME-291 - replies duplicated in streams and public timeline From: Ethan Jewett To: esme-dev Content-Type: multipart/alternative; boundary=0016364163eb7cfe100492e60240 X-Virus-Checked: Checked by ClamAV on apache.org --0016364163eb7cfe100492e60240 Content-Type: text/plain; charset=ISO-8859-1 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? Ethan --0016364163eb7cfe100492e60240--