Re: [Tools-discuss] another case of links not updating

Paul Wouters <paul@nohats.ca> Wed, 06 May 2020 17:58 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA703A0948 for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 10:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 Z2B9K46_sd3Y for <tools-discuss@ietfa.amsl.com>; Wed, 6 May 2020 10:58:34 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A28283A0954 for <tools-discuss@ietf.org>; Wed, 6 May 2020 10:58:34 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 49HPTj2JyxzF5g; Wed, 6 May 2020 19:58:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1588787913; bh=imlXLgn5HJUmxPAf5p/t+J6RtK3EN0zwuL5Q8X4PETI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Apg0Dqr6PspogevEnTbtiABARVWWihR0Ggq/MJy7B9/KSdPOvAmXEu9/DL9AYr1+X Blxt2HBblU5gecJ52e5aIxjylzYZSjUIptXlpKiBNwEnlgeVngfP5JBicdm5oEEazj dtQgCkpil2kLk6rOAsFLTYEIMqhm1gnLr4lbQb4A=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id XOzR7GqU14-e; Wed, 6 May 2020 19:58:32 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 6 May 2020 19:58:32 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 27A266029BA6; Wed, 6 May 2020 13:58:31 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 23EE266B7C; Wed, 6 May 2020 13:58:31 -0400 (EDT)
Date: Wed, 6 May 2020 13:58:31 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Henrik Levkowetz <henrik@levkowetz.com>
cc: tools-discuss@ietf.org
In-Reply-To: <d538a7da-8e90-cf26-3c39-b0dd5b2241b9@levkowetz.com>
Message-ID: <alpine.LRH.2.21.2005061352200.20509@bofh.nohats.ca>
References: <alpine.LRH.2.21.2005061024040.16512@bofh.nohats.ca> <d538a7da-8e90-cf26-3c39-b0dd5b2241b9@levkowetz.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/mfDaiDbSgUk4uTChNun4_ZcwnwQ>
Subject: Re: [Tools-discuss] another case of links not updating
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2020 17:58:37 -0000

On Wed, 6 May 2020, Henrik Levkowetz wrote:

Thanks for the quick rpely Henrik,

>> It's not a "timing" thing either as the -04 was submitted on April 30.
>
> Right.  It's a matter of a cache invalidation trigger sometimes failing.

Yes, I remember talking about this before. But that trigger bug only
reflects to recent updates. All the past issues where the trigger did
not happen would need to be found and corrected as well.

So I thought the solution we thought of at that time was to go over the
entire archive and fixup all the broken ones automatically. That would
be independent of this cache bug or other future bugs ?

> The metadata handling and cache invalidation on tools.ietf.org resides in
> old bash scripts that have not gotten a lot of attention lately, to a
> large extent because my time has been dedicated to datatracker and xml2rfc
> work the last few years.  With the importance of getting the xml2rfc schema
> v3 launced and the effort of moving other tools to the datatracker, the
> maintenance of the tools.ietf.org site has fallen behind.

I do understand and I do appreciate the time you spend on xml2rfc, as
I'm a frequent user of it. But I do think this bug needs a bit more
priority, since it has been years, and I only find out about missing
references on my own drafts. It is really unclear how many references I
miss on other people's drafts when I don't know they exist because the
tracker might not show me. Personally, now when I read a "latest" draft,
I always increase the number by one to see if I'm not missing something :/

> It's work I want to do, but the hours I have are limited.  I've fixed the
> immediate issue, and will try to find time to debug the root cause.

Thanks. I'll ping you again when I have some more time myself in a few
weeks to see if we can get me setup to look at the current code and/or
dbase to see the scope of the issue and look at fixing the bug and the
old references.

Cheers,

Paul