Tom Hughes

Which is the duration of the upstream timeout so I guess that is firing but cloudflare is replacing the rails error with it's own.

Yes if people created stupid relations you're probably not going to be able to view them on the web site because we have timeouts in place to protect the service.

Getting rid of account creation seems like an entirely backward way to satisfy that policy requirement, even if we accept that an creating an account on a web page triggered...

But what's the solution? I'm certainly not interested in removing the account creation option because we want people to be able to signup! Is the answer that clients shouldn't be...

Looks like this is a no-go until we can move to ruby 3.1 then...

Not sure why you're getting those messages because I don't see them. I mean I can see what the problem is - people have written stubs for tests that don't...

In some cases they're not even stubs - a test of an action with no assertions still checks that a given action will run without throwing any exceptions.

Yes I figured it out... I had `RUBYOPT` set to suppress warnings in my environment. I think at some point there were some annoying warnings we couldn't get rid of...

There's an extra complication which is that we can't (yet) use the GitHub 24.04 image to run tests as it's still beta and is missing firefox (planned to be fixed...

Also we're waiting on https://github.com/jumph4x/canonical-rails/pull/92 before we can go to 7.2.1 which is already out.