- Issue created by @alexpott
- Status changed to Needs review
almost 2 years ago 12:35am 25 January 2023 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
This is going to be a hard one to prove :)
- Status changed to RTBC
almost 2 years ago 5:45pm 13 February 2023 - 🇺🇸United States smustgrave
Interesting bug to find!
Seems like a good update.
- 🇧🇷Brazil kleiton_rodrigues Americana/SP
The #2 patch applies cleanly.
$request_time = $this->container->get('datetime.time')->getCurrentTime();
looks god to me. -
longwave →
committed 7614d551 on 10.0.x
Issue #3336283 by alexpott: Drupal\Tests\datetime\Functional\...
-
longwave →
committed 7614d551 on 10.0.x
-
longwave →
committed 97fd6ea2 on 10.1.x
Issue #3336283 by alexpott: Drupal\Tests\datetime\Functional\...
-
longwave →
committed 97fd6ea2 on 10.1.x
-
longwave →
committed 3507ab53 on 9.5.x
Issue #3336283 by alexpott: Drupal\Tests\datetime\Functional\...
-
longwave →
committed 3507ab53 on 9.5.x
- 🇬🇧United Kingdom longwave UK
There is still the possibility of a date change between reading the time and the next page request, but I agree that the gap is a lot smaller this way around and so this should reduce random failures.
Committed and pushed 97fd6ea2a9 to 10.1.x and 7614d551c9 to 10.0.x and 3507ab53fd to 9.5.x. Thanks!
- Status changed to Fixed
almost 2 years ago 7:44pm 12 March 2023 Automatically closed - issue fixed for 2 weeks with no activity.