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 AM 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 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 AM Magnus Hagander <magnus@hagander.net> 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 <me@jeltef.nl> 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 <magnus@hagander.net> 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 > >
