Re: [iola-conversion-tool] Several problems with HTML agenda page

Ole Laursen <olau@iola.dk> Mon, 05 March 2012 20:43 UTC

Return-Path: <olau@iola.dk>
X-Original-To: iola-conversion-tool@ietfa.amsl.com
Delivered-To: iola-conversion-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911E611E80BD for <iola-conversion-tool@ietfa.amsl.com>; Mon, 5 Mar 2012 12:43:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.829
X-Spam-Level:
X-Spam-Status: No, score=-2.829 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ScHTCw7I74QD for <iola-conversion-tool@ietfa.amsl.com>; Mon, 5 Mar 2012 12:43:44 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E983921F891B for <iola-conversion-tool@ietf.org>; Mon, 5 Mar 2012 12:43:43 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so4350267vbb.31 for <iola-conversion-tool@ietf.org>; Mon, 05 Mar 2012 12:43:43 -0800 (PST)
Received-SPF: pass (google.com: domain of olau@iola.dk designates 10.52.22.166 as permitted sender) client-ip=10.52.22.166;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of olau@iola.dk designates 10.52.22.166 as permitted sender) smtp.mail=olau@iola.dk
Received: from mr.google.com ([10.52.22.166]) by 10.52.22.166 with SMTP id e6mr38780910vdf.5.1330980223505 (num_hops = 1); Mon, 05 Mar 2012 12:43:43 -0800 (PST)
Received: by 10.52.22.166 with SMTP id e6mr33204016vdf.5.1330980223253; Mon, 05 Mar 2012 12:43:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.156.18 with HTTP; Mon, 5 Mar 2012 12:43:23 -0800 (PST)
In-Reply-To: <4F550E88.9070203@nostrum.com>
References: <4F550E88.9070203@nostrum.com>
From: Ole Laursen <olau@iola.dk>
Date: Mon, 5 Mar 2012 21:43:23 +0100
Message-ID: <CANb2Ov+9OaMapmJvq0KTPxiZ54CYxBZZhztJvc_jt_3yT+79jQ@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmrZ5MQuiISjWlwStgioyvwU6dQZyPdxoAN8MA+rdYAvzu5gZwBhOoJ6Xpdip6h37CERveY
Cc: iola-conversion-tool@ietf.org
Subject: Re: [iola-conversion-tool] Several problems with HTML agenda page
X-BeenThere: iola-conversion-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <iola-conversion-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iola-conversion-tool>
List-Post: <mailto:iola-conversion-tool@ietf.org>
List-Help: <mailto:iola-conversion-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 20:43:45 -0000

Hi,

Thanks for the thorough report! I believe the first 3 issues have been
fixed recently. I suspect Henrik will deploy the fixes soon.

2012/3/5 Adam Roach <adam@nostrum.com>om>:
> Problem 4: Although it does not show up on the 83 agenda, there is something
> wrong with the characterization of the IRTF meeting for IETF 82 (see
> https://datatracker.ietf.org/meeting/82/agenda.html#RAI) such that it is
> displayed by default. If this is simply a data import error for IETF 82,
> then it's no big deal.

The data looks fine to me, but the proxy didn't handle the IRTF group
specially. It looks like the old code was giving it an area of "irtf".
I've fixed the proxy to do the same (will be online when Henrik
deploys it).

> Problem 5: The multi-draft PDF function appears to have been broken. Go to
> https://datatracker.ietf.org/meeting/agenda.html#tsvwg and scroll down to
> the TSVWG session. Just above the agenda, on the right, click on the "pdf"
> link. Instead of getting a PDF file, you'll get a 404 error. This is true
> also of the tar file link right next to it.

I was really confused by this, but it turns out it works fine for
meeting 82. So I think the problem is that this part of the code isn't
querying the session for the agenda path, but trying to deduce it in
various ways which now fail with the newly uploaded agendas. I'll see
if I can get that fixed tomorrow, it's getting a little late.


Ole