Repository navigation
[BUGFIX] Persist immutable timezone conversions - #640
Merged
Merged
Conversation
sfroemkenjw
approved these changes
Sep 7, 2026
Contributor
|
thank you for taking care of that. Merged Stefan |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a logic error when converting immutable event dates to the configured timezone.
DateTimeImmutable::setTimezone() returns a new instance.
The extension discarded that return value, so the timezone conversion was never persisted.
As a result, the same conversion branch ran repeatedly and PHP 8.5 emitted excessive warnings, causing log flooding in PHP 8.5 due to its method marked there with
#[\NoDiscard]The actual bug existed with versions prior to PHP 8.5 as well, just with no warnings.