Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7A61710E5B for ; Fri, 24 Jan 2014 16:53:25 +0000 (UTC) Received: (qmail 9881 invoked by uid 500); 24 Jan 2014 16:53:25 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 9859 invoked by uid 500); 24 Jan 2014 16:53:25 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 9846 invoked by uid 99); 24 Jan 2014 16:53:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 16:53:24 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 16:53:20 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:References:In-Reply-To:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=6ZGHGNFjZEVZPEGHBeCv1Hg8GOCsQ644SoFUapr1YM0=; b=Fbh6t/FIrMFss4IusYcsiSRftRRXpeywKLdtTH5k+PnTM/kMP6KXCRl0E0L3Ec+IOzXQbUyAYy18F5N9C/XFDng1W6uQA9ji6BufxsIlhPFRnk7qJRBCnIU09ZZVixob8/BBEifQjpd5Sk1sEy5YBkVuTLRGy4L7TVZAEhn4BJ0=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W6k03-0008GQ-Ow for allura-dev@incubator.apache.org; Fri, 24 Jan 2014 16:52:59 +0000 Content-Type: multipart/related; boundary="===============6691080981760569671==" MIME-Version: 1.0 To: allura-dev@incubator.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <7047@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #7047 ticket bulk_edit task sometimes doesn't call add_artifacts Message-ID:

In-Reply-To: <52d058a7bcf63a676a0e3da8.tickets@allura.p.sourceforge.net> References: <52d058a7bcf63a676a0e3da8.tickets@allura.p.sourceforge.net> Date: Fri, 24 Jan 2014 16:52:59 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6691080981760569671== Content-Type: multipart/alternative; boundary="===============4158864731731306991==" MIME-Version: 1.0 --===============4158864731731306991== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **status**: code-review --> validation - **QA**: Dave Brondsema --- ** [tickets:#7047] ticket bulk_edit task sometimes doesn't call add_artifacts** **Status:** validation **Created:** Fri Jan 10, 2014 08:31 PM UTC by Dave Brondsema **Last Updated:** Fri Jan 24, 2014 04:40 PM UTC **Owner:** Cory Johns On Allura's own ticket tracker when I do a bulk edit, it lately has been not updating solr with the ticket changes. This has happened a few times, but I haven't been able to reproduce on a test project or locally. Here's the tasks that run in such a case: https://sourceforge.net/p/allura/pastebin/52d057cbea406b5dc88d20ec And here's the tasks that run when it does work properly: https://sourceforge.net/p/allura/pastebin/52d057d404161f105486b39c In the case of it not working, the sendmail events and logging of ticket version commits show that the tickets were found. I can even find the corresponding zarkov events that ArtifactSessionExtension.after_flush sends out, so all I can figure is that "arefs" was falsey. But i don't see how that can happen. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============4158864731731306991== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • status: code-review --> validation
  • QA: Dave Brondsema

[tickets:#7047] ticket bulk_edit task sometimes doesn't call add_artifacts

Status: validation
Created: Fri Jan 10, 2014 08:31 PM UTC by Dave Brondsema
Last Updated: Fri Jan 24, 2014 04:40 PM UTC
Owner: Cory Johns

On Allura's own ticket tracker when I do a bulk edit, it lately has been not updating solr with the ticket changes. This has happened a few times, but I haven't been able to reproduce on a test project or locally.

Here's the tasks that run in such a case: https://sourceforge.net/p/allura/pastebin/52d057cbea406b5dc88d20ec

And here's the tasks that run when it does work properly: https://sourceforge.net/p/allura/pastebin/52d057d404161f105486b39c

In the case of it not working, the sendmail events and logging of ticket version commits show that the tickets were found. I can even find the corresponding zarkov events that ArtifactSessionExtension.after_flush sends out, so all I can figure is that "arefs" was falsey. But i don't see how that can happen.

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============4158864731731306991==-- --===============6691080981760569671==--