Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWtFa-002qr9-Fa for pgsql-www@arkaria.postgresql.org; Wed, 02 Jul 2025 08:55:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uWtEZ-00DH2A-Ct for pgsql-www@arkaria.postgresql.org; Wed, 02 Jul 2025 08:54:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWtEZ-00DH20-4g for pgsql-www@lists.postgresql.org; Wed, 02 Jul 2025 08:54:27 +0000 Received: from mail-yb1-xb34.google.com ([2607:f8b0:4864:20::b34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uWtEX-005GnN-1T for pgsql-www@lists.postgresql.org; Wed, 02 Jul 2025 08:54:27 +0000 Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-e81f8679957so3348846276.2 for ; Wed, 02 Jul 2025 01:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander.net; s=mail; t=1751446463; x=1752051263; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u9FivjpDtrPwDKm/ch/g9mFoS04GjgCBMwziuyEHo8M=; b=YKg9E4zV8F3rBrR2eeQmSQF74tIncy5miugZnYq+RIPHkuVyRe49ldp27GiOaA22kw YOHZj4T45oGoiUGMkPdlYJQS5W4jSCfEHLdyXhFQ8/h4lo/zMTlOMAKyk2HB+KBhxumu Z2OavcJwVsWKmLM216u4P+LjKodWXPjQWuUaAHl0ksa6e6bDxxaAFXs/tvYpjuR7eUN7 awG/JYCfeyr2aJfidpVXoGc9VsPcr8QDnQ+PQfFw0xV53ngX+WD8+JcZHanyMTTqdtH3 VhWXKj3LUbWtYu68PEbGLhh/K8pkFQu7uVWO56Mv9cHVIl3YZIcSNcV63xhCcDh3fyvx 35Yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751446463; x=1752051263; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u9FivjpDtrPwDKm/ch/g9mFoS04GjgCBMwziuyEHo8M=; b=UQEEEHqxVhvbfOm6bmqJzA220K4xyCdeib7EjSlzdweT+XuQaS/c110pSySJfipry+ OAqc+tYTMgteo+ubIw5cGAc2a9GBgAKmEaPeJnWR8tbQvdFr7kLqppLz8XZO6P4vgvy+ 8FI4qNJ+dZdjQuJ/NyDL+WX8oiOBmGTgdRb/dtBKzj9M/clIJtAt6vmYIWKoZ80yTpKh HM4HVkHK2znSzkOfPDZd5DnfiXv09/34yMsuxYair6G03ixV0zBqkciovrol+My3DSWK STkdEzECcZjutIWS/8QTTCrvrNcfIlq4gVSzx9hMkthf6CXiLnaGlF2IsCB8leKUQcwt sKHg== X-Gm-Message-State: AOJu0YyAnaW+7jmMHaCzm/Xx0QyftDH3gEI/0EvkZOE6atSUReYVuDvW tFc0DefYn/OCkuDj5iPxwtXywNST7q2AkxVD1Q6LVOqZJXFH96bYf4rb9gCkHd7elmO4yMKBpHi 7hKSvh1fZExhPZ/ziMciZZi8Nmw9BK0ruu4snB5k0bPTAnuRQHcE= X-Gm-Gg: ASbGncsR/uSqnOFryyj5f4CHfOEnJ1Y1qVT8cT5dlPMU1uNyIKKuMe2e4snLd/rcT4C xXsQFGFGHKyxaOkhtbMBMEcHMnCMFH5+UDpRm7C0DvBLhRyxKBreWcTyWWNlrzirxqEodY0tsDj z5lXhKGGVSLOZZypM1ok0iN34HHIIpoU6jEGk0y2o62zIKNQ== X-Google-Smtp-Source: AGHT+IFJTMJxHFa0XdQ+ZIvrDDxVHt+7LS7w1YtokyuUmOxWXtOEPBCBfHNDnhGC4KWYEBQNSUss/Lh4o81CxxlisLg= X-Received: by 2002:a05:6902:4892:b0:e85:efe5:4163 with SMTP id 3f1490d57ef6-e897e220249mr2123171276.37.1751446463423; Wed, 02 Jul 2025 01:54:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Magnus Hagander Date: Wed, 2 Jul 2025 10:54:11 +0200 X-Gm-Features: Ac12FXxGJbnTcdB4WZS-49pkEfOUs5u8WpeAGzWjqtIcYi05kdbBTW8eHO655GM Message-ID: Subject: Re: Cf app crashes To: Jelte Fennema-Nio Cc: PostgreSQL WWW Content-Type: multipart/alternative; boundary="0000000000004bb4d10638ee6828" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004bb4d10638ee6828 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hmm, are you saying you're changing something at the *source* of the calls? Surely the bug is in the code that curn the cf app as that's the one that crashdumps? And either way I'm still seeing the errors come in at 10:50, which is 14 minutes after you sent that email, so I think it's still broken. //Magnus On Wed, Jul 2, 2025 at 10:36=E2=80=AFAM Jelte Fennema-Nio wr= ote: > I think maybe it's fixed now. Restarted the new cfbot API endpoint, > hopefully that was the reason my code change did not have the intended > effect. > > On Wed, 2 Jul 2025 at 10:28, Magnus Hagander wrote: > > > > Moving the discussion over to this thread, as your reply to my forward > ended up threaded in with all the error messages and I missed it (gmail > breaks off the threading after 100 mails..) :) > > > > The errors are still happening, so your fix didn't take. > > > > //Magnus > > > > On Wed, Jul 2, 2025 at 9:07=E2=80=AFAM Magnus Hagander > wrote: > >> > >> Done! > >> > >> Will investigate why you didn't get the automatic reports later today. > >> > >> /Magnus > >> > >> On Wed, Jul 2, 2025, 09:04 Jelte Fennema-Nio wrote: > >>> > >>> I have not received any messages related to crashes, so yes please > >>> forward one/some of them. I did indeed receive emails for crashes in > >>> the past, so either these are a different kind, or the previous setup > >>> got broken somehow. > >>> > >>> On Wed, 2 Jul 2025 at 08:57, Magnus Hagander > wrote: > >>> > > >>> > We've seen about 250 crash dumps from the cf app since last night. = I > assume you've seen those? Iirc we did get it set up so you get a direct > copy, or do you need me to forward something? > >>> > > >>> > > >>> > /Magnus > > > > > --0000000000004bb4d10638ee6828 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hmm, are you saying you're chang= ing something at the *source* of the calls? Surely the bug is in the code t= hat curn the=C2=A0cf app as that's the one that crashdumps?
<= br>
And either way I'm still seeing the errors come in at 10:= 50, which is 14 minutes after you sent that email, so I think it's stil= l broken.

//Magnus

On Wed, Jul 2, 2025 at 10:36=E2= =80=AFAM Jelte Fennema-Nio <me@jeltef.nl> wrote:
I think maybe it's fixed now. Restarted the new cfbot= API endpoint,
hopefully that was the reason my code change did not have the intended
effect.

On Wed, 2 Jul 2025 at 10:28, Magnus Hagander <magnus@hagander.net> wrote:
>
> Moving the discussion over to this thread, as your reply to my forward= ended up threaded in with all the error messages and I missed it (gmail br= eaks off the threading after 100 mails..) :)
>
> The errors are still happening, so your fix didn't take.
>
> //Magnus
>
> On Wed, Jul 2, 2025 at 9:07=E2=80=AFAM Magnus Hagander <magnus@hagander.net> w= rote:
>>
>> Done!
>>
>> Will investigate why you didn't get the automatic reports late= r today.
>>
>> /Magnus
>>
>> On Wed, Jul 2, 2025, 09:04 Jelte Fennema-Nio <me@jeltef.nl> wrote:
>>>
>>> I have not received any messages related to crashes, so yes pl= ease
>>> forward one/some of them. I did indeed receive emails for cras= hes in
>>> the past, so either these are a different kind, or the previou= s setup
>>> got broken somehow.
>>>
>>> On Wed, 2 Jul 2025 at 08:57, Magnus Hagander <magnus@hagander.net> wro= te:
>>> >
>>> > We've seen about 250 crash dumps from the cf app sinc= e last night. I assume you've seen those? Iirc we did get it set up so = you get a direct copy, or do you need me to forward something?
>>> >
>>> >
>>> > /Magnus
>
>

--0000000000004bb4d10638ee6828--