IETF Logo Mail Archive

[Tools-discuss] bibxml3 database reload frequency

Kent Watsen <kent+ietf@watsen.net> Thu, 20 August 2020 16:05 UTC

Return-Path: <010001740c9e6adf-5f978dea-f19a-4298-8376-b82bf3be0835-000000@amazonses.watsen.net>
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 DE5A53A085A for <tools-discuss@ietfa.amsl.com>; Thu, 20 Aug 2020 09:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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=amazonses.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 hKTJoUiy3TUj for <tools-discuss@ietfa.amsl.com>; Thu, 20 Aug 2020 09:05:44 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65D593A0841 for <tools-discuss@ietf.org>; Thu, 20 Aug 2020 09:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1597939543; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:To:Feedback-ID; bh=byRJiJ+pImQYNl7rsH6KkIDDokYYk1dCmkxiFl24ZTk=; b=X8MEP9XBV61rWynqxtm1MMe6EqTO4uVfKCMlX7jq5T3B8m9urodSkm5TS3xoJoqu 79i2DAzbAlJyzgh7zQ5G1fI6dezN07AxB2HxnCg8v3Ql4aI74Z3YlfifdJjaTVtG71N uplDcs+O9THZ2J3WO8RbmPFFTVusHPNphHcjyrUM=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4A90E61D-E33A-4FD1-B869-9FE4D40A4A7D"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-ID: <010001740c9e6adf-5f978dea-f19a-4298-8376-b82bf3be0835-000000@email.amazonses.com>
Date: Thu, 20 Aug 2020 16:05:42 +0000
To: tools-discuss@ietf.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-SES-Outgoing: 2020.08.20-54.240.8.96
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/2zRLHajdjDmDWA7lODHz2ebJObs>
Subject: [Tools-discuss] bibxml3 database reload frequency
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: Thu, 20 Aug 2020 16:05:47 -0000

Hi Tools Team.

How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 rebuilt?  Is there a way to have it rebuild more often and/or for draft authors to externally prompt it to rebuild?

See below for background info.

Thanks,
Kent


Background:

I have one draft depending on another.  The new <relref> element is used, but the resulting hyperlinks point to the previous version of the referenced draft (before it was updated ~1 hour ago).

Looking at https://xml2rfc.tools.ietf.org/public/rfc <https://xml2rfc.tools.ietf.org/public/rfc>, I see that “bibxml3” hasn’t been updated for roughly one day:

	bibxml3/	19-Aug-2020 00:49

Note that the timestamp for “bibxml” (without the ‘3’) is roughly 24 hours newer:

	bibxml/	20-Aug-2020 00:45

In any case, the hyperlinks produced by the <relref> elements are all resolving to the previous version of the referenced draft.   I tried `xml2rfc —clear-cache`, but I think the source issue is with https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 not having updated…

How often is https://xml2rfc.tools.ietf.org/public/rfc/bibxml3 built?  Is there a way to prompt it to reload?

v2.23.0 | Report a Bug | By Email