IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker

Robert Sparks <rjsparks@nostrum.com> Thu, 16 May 2019 15:49 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7861200FC for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 08:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXH7AXRWX2kQ for <tools-development@ietfa.amsl.com>; Thu, 16 May 2019 08:49:36 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D33C120074 for <tools-development@ietf.org>; Thu, 16 May 2019 08:49:36 -0700 (PDT)
Received: from unescapeable.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x4GFnZuZ075784 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <tools-development@ietf.org>; Thu, 16 May 2019 10:49:36 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1558021776; bh=U9p2j2cDqO1CG9CXv5J7uVJcDTl6ZJNSY2CdczuMmXM=; h=Subject:To:References:From:Date:In-Reply-To; b=CJxJ3jfBxe8UR4AFGx7ixChSAMh3rq/2YD9WVpLDdYtUf5y1wcJicLf38ShShnEBc WtF77o57p624W1Mj3WMKJi/4bttUVHfmJGJ6wF/3V/b7H7fOOcclyvGikq+B/UpLT+ kot2aCXRiz4F0Ql4So1VU1LGvdKStZbTkyJP5FVs=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unescapeable.local
To: tools-development@ietf.org
References: <359EC4B99E040048A7131E0F4E113AFC01B3367E08@marathon> <7fe8c740-90e8-895f-7ef8-321192de6502@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <2404589b-6eca-5524-f50f-0e26daca0b45@nostrum.com>
Date: Thu, 16 May 2019 10:49:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <7fe8c740-90e8-895f-7ef8-321192de6502@nostrum.com>
Content-Type: multipart/alternative; boundary="------------48BC195C2689199DB45C7BEA"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/BF4TCkLkBl3cpcV7YBZ1NvVq6c8>
Subject: Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 15:49:39 -0000

So the direct answer is simpler than I expected. It is the last change 
in iesg state (or the date iesg-evaluation started).

The relevant code is here:

<https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/ietf/doc/templatetags/ballot_icon.py#L168>

at line 168.

RjS

On 5/16/19 9:23 AM, Robert Sparks wrote:
>
> Hi Roman -
>
> Like Russ, I will have to look at the code to give you the exact 
> answer you are looking for, and I hope to do that today or tomorrow. I 
> fear the answer will be "it's complicated".
>
> For the moment, I can point to some history. Different ADs over time 
> have had different opinions about what these "since" values should 
> represent. Should it show time since last action, or accrued time in 
> the where it is in the queue? Who is the metric there to help push 
> along? I've occasionally been of the opinion that perhaps we should 
> show state and sub-state staleness separately (as suggested by Adrian 
> in one of the tickets below), but the display does get cluttered...
>
> See
>
> <https://trac.tools.ietf.org/tools/ietfdb/ticket/1371> and
>
> <https://trac.tools.ietf.org/tools/ietfdb/ticket/1372>
>
> RjS
>
>
> On 5/16/19 8:31 AM, Roman Danyliw wrote:
>> Hi!
>>
>> At the IESG retreat, there was a confusion in the IESG about how the timer listed next to the draft  (e.g., "for xxx days") in the datatracker is reset when a state or sub-state changes (see screenshot).  I was asked get clarity on the following:
>>
>> ** Which sub-state changes will trigger a reset to 0?
>>
>> ** Which state changes will trigger a reset to 0?
>>
>> Thanks,
>> Roman
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

v2.23.0 | Report a Bug | By Email