Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3410450
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3410450-random-performance-test
changes, plain diff MR !5932
Comments
Comment #2
catch#3410312: Flood database backend ::isAllowed() should call ::ensureTableExists() likely caused this. The exceptions in the lazy creation table logic mean that the original query that triggered the exception (like FloodInterface::isAllowed()) don't get recorded, so that issue removes less observable queries than it does actual queries that run during tests.
Comment #4
larowlanThanks
Comment #5
catchThis ended up being included in #3410419: Only clear flood attempts when necessary during user login which I wasn't expecting to land first.
Comment #6
catchNo we do need to tweak it after all. https://git.drupalcode.org/project/drupal/-/jobs/529691
Comment #7
heddnHopefully this is enough.
Comment #10
larowlanCommitted to 11.x
Backported to 10.2.x because the related issues also were, so I assume the issue also exists there.