InvalidArgumentException: The timestamp must be numeric. in Drupal\Component\Datetime\DateTimePlus::createFromTimestamp()

+1 for error, i will review patch

Patch applied cleanly and fix the issue, Issue also reported in published_date module see https://www.drupal.org/project/publication_date/issues/3424575 🐛 InvalidArgumentException: The timestamp must be numeric. in Drupal\Component\Datetime\DateTimePlus::createFromTimestamp() (line 201 of /var/www/html/www/core/lib/Drupal/Component/Datetime/DateTimePlus.php). Active

This looks like a workaround. How did this become a Core bug?

I agree with #6. And there has been no response for more information here for 4 months so I am closing this as works as designed.

If you show this is a core bug, then add a comment and reopen the issue.

Thanks!

Patch updated to Drupal version 10.3.1.

I'm seeing this error on a site running Drupal 10.3.4 when I try to look at revisions for a taxonomy term. The revision in question is returning null for getRevisionCreationTime(), and that is leading to the exception described in this issue. I am not able to reproduce it on a clean Drupal 10 install, which leads me to suspect that the problem of the null revision creation time might be an artifact of upgrading this site over the years from Drupal 8 to 9 to 10.

I don't know whether this is a one-off or some obscure upgrade bug, so I don't think it's worth reopening the issue. Documenting what I found in case it's helpful to somebody else.

Hello

With "revision" check, the errors fixed like before proposed:
file:
core/lib/Drupal/Core/Entity/Controller/VersionHistoryController.php

code:

protected function getRevisionDescription(RevisionableInterface $revision): array {
    $context = [];
    if ($revision instanceof RevisionLogInterface  ) {

replace to code:

protected function getRevisionDescription(RevisionableInterface $revision): array {
    $context = [];
    if ($revision instanceof RevisionLogInterface && !empty($revision->getRevisionCreationTime() ) ) {

Regards

Hi ,
I got this issue when i upgraded my project to 10.3.x. As suggested by @ordasoft , code changes in #10 worked for me. I have created the patch with changes from #10.

Regards,