Roundup Tracker - Issues

Message7473

Author schlatterbeck
Recipients marcus.priesch, rouilj, schlatterbeck
Date 2022-04-28.09:38:13
Message-id <20220428093811.l6y4srn5qt4bzxcw@runtux.com>
In-reply-to <25ac0c28-9573-6cfe-9cb9-b208e774c7e9@priesch.co.at>
On Thu, Apr 28, 2022 at 08:37:14AM +0000, Marcus Priesch wrote:

> ps: do you have anything i can test against the preloading stuff?

Hmm, not really. The original issue was issue2551172 where the rev
multilinks were only there on the first request (with the standalone
roundup_server) but not on subsequent requests when the connection was
cached. The problem did *not* materialize with WSGI. And the first
request after the cached connection timed out was OK again.

So I really don't know how to come up with an easy test for this.
Especially when WSGI is involved (although *this* problem didn't occur
with WSGI another one might be specific to WSGI).

But maybe your patches make the code *less* brittle in this part so that
the tracker (as opposed to the DB) is only always initialized once on
startup -- for WSGI or other frontends.

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com
History
Date User Action Args
2022-04-28 09:38:14schlatterbecksetrecipients: + schlatterbeck, rouilj, marcus.priesch
2022-04-28 09:38:14schlatterbecklinkissue2551184 messages
2022-04-28 09:38:13schlatterbeckcreate