launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxx>]

I wasn't getting these last week, but suddenly I am getting bounces
again when I comment on loggerhead merge proposals. So it seems the
problem has cropped up again.  (Or, maybe I just didn't comment
specifically on loggerhead since John's mail, and it's just still
active.)

At some level this might be connected to the different outgoing mail
header settings between bugs and reviews.

Martin


Received: from localhost ([127.0.0.1] helo=chlorine.canonical.com)
	by chlorine.canonical.com with esmtp (Exim 4.71)
	(envelope-from <launchpad-bugs-bounces@xxxxxxxxxxxxxxxxxxx>)
	id 1PvM6g-0007nb-RJ
	for mbp@xxxxxxxxxxxxxx; Fri, 04 Mar 2011 03:55:10 +0000
Subject: Re: [Merge] lp:~jameinel/loggerhead/less_work_for_head_716217
 into	lp:loggerhead
From: launchpad-bugs-owner@xxxxxxxxxxxxxxxxxxx
To: mbp@xxxxxxxxxxxxxx
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7864264032856119061=="
Message-ID: <mailman.14117.1299210910.26923.launchpad-bugs@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 04 Mar 2011 03:55:10 +0000
Precedence: bulk
X-BeenThere: launchpad-bugs@xxxxxxxxxxxxxxxxxxx
X-Mailman-Version: 2.1.13
List-Id: Launchpad Bug Reports <launchpad-bugs.lists.canonical.com>
X-List-Administrivia: yes
Sender: launchpad-bugs-bounces@xxxxxxxxxxxxxxxxxxx
Errors-To: launchpad-bugs-bounces@xxxxxxxxxxxxxxxxxxx

--===============7864264032856119061==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

Your message was rejected


--===============7864264032856119061==
Content-Type: message/rfc822
MIME-Version: 1.0

Received: from adelie.canonical.com ([91.189.90.139])
	by chlorine.canonical.com with esmtp (Exim 4.71)
	(envelope-from <bounces@xxxxxxxxxxxxx>)
	id 1PvM6f-0007nR-40
	for launchpad-bugs@xxxxxxxxxxxxxxxx; Fri, 04 Mar 2011 03:55:09 +0000
Received: from loganberry.canonical.com ([91.189.90.37])
	by adelie.canonical.com with esmtp (Exim 4.71 #1 (Debian))
	id 1PvM6f-000434-0i
	for <launchpad-bugs@xxxxxxxxxxxxxxxx>; Fri, 04 Mar 2011 03:55:09 +0000
Received: from loganberry.canonical.com (localhost [127.0.0.1])
	by loganberry.canonical.com (Postfix) with ESMTP id 011B82E8103
	for <launchpad-bugs@xxxxxxxxxxxxxxxx>; Fri,  4 Mar 2011 03:55:09 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Launchpad-Message-Rationale: Reviewer @loggerhead-team
X-Launchpad-Notification-Type: code-review
X-Launchpad-Branch: ~jameinel/loggerhead/less_work_for_head_716217
In-Reply-To: <20110303120224.27865.8949.codereview@xxxxxxxxxxxxxxxxxxxx>
Reply-To: mp+49182@xxxxxxxxxxxxxxxxxx
Message-Id: <AANLkTi=_HwA-Pz+RXL8rGPCyrDN7B5G=hNie=VAMq830@xxxxxxxxxxxxxx>
X-Launchpad-Project: loggerhead
To: John A Meinel <john@xxxxxxxxxxxxxxxxx>
From: Martin Pool <mbp@xxxxxxxxxxxxxx>
Subject: Re: [Merge] lp:~jameinel/loggerhead/less_work_for_head_716217 into
	lp:loggerhead
Date: Fri, 04 Mar 2011 03:55:08 -0000
Sender: bounces@xxxxxxxxxxxxx
Errors-To: bounces@xxxxxxxxxxxxx
Precedence: bulk
X-Generated-By: Launchpad (canonical.com); Revision="12515";
	Instance="initZopeless config overlay"
X-Launchpad-Hash: ac9d4c31267971f54c964b372f7f59ed2b62e5b7

On 3 March 2011 23:04, John A Meinel <john@xxxxxxxxxxxxxxxxx> wrote:
> Should we kick this back? I'd like to leave it, pending evaluation of whe=
ther the HEAD requests are significant overhead. history-db also reduces th=
e base overhead.

If by kick it/leave it you mean just do nothing with it until we see
that cutting the cost of HEAD requests are really worthwhile, that's
ok with me.  We can just mark it rejected and leave it attached to the
bug.

Sorry for sending you on a wild goose chase; I didn't think enough
about the fact that getting a realistic result might mean taking it
most of the way through rendering.  I don't think cutting the cost of
initial GET is a good tradeoff to speed up later HEAD requests.

I do think it's worthwhile/important that HEAD not actually send a
body back, because that clearly is violating the rfc in a fairly
fundamental way.  Just generating and discarding it is ok with me.

It seems like eventually to be able to stream the body we would need
to be able to tell before rendering whether the request is ultimately
likely to succeed or not.

-- =

https://code.launchpad.net/~jameinel/loggerhead/less_work_for_head_716217/+=
merge/49182
Your team Loggerhead-team is requested to review the proposed merge of lp:~=
jameinel/loggerhead/less_work_for_head_716217 into lp:loggerhead.


--===============7864264032856119061==--