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

Henrik Levkowetz <> Wed, 06 May 2020 18:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 217763A0991 for <>; Wed, 6 May 2020 11:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aV5v1hOB1oDV for <>; Wed, 6 May 2020 11:09:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6E0DB3A098A for <>; Wed, 6 May 2020 11:09:54 -0700 (PDT)
Received: from ([]:57836 helo=tannat.localdomain) by with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1jWOUT-0003JW-P0; Wed, 06 May 2020 11:09:54 -0700
To: Paul Wouters <>
References: <> <> <>
From: Henrik Levkowetz <>
Message-ID: <>
Date: Wed, 6 May 2020 20:09:46 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EbU98GmwJnsWWXShHXsDsiKM4KuJn1vVr"
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <>
Subject: Re: [Tools-discuss] another case of links not updating
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 06 May 2020 18:09:56 -0000

Hi Paul,

On 2020-05-06 19:58, Paul Wouters wrote:
> 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 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 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 :/

Ouch.  Ok, point taken.

>> 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.


Best regards,