Views NumericField round must be of type int|float

@evonasek thanks for reporting your issue.

We only set issues to 'fixed' once they have been committed, so moved this back.

Can you provide example code or steps of how to trigger this with just Drupal core? Often when these issues occur it is due to bad data being supplied by custom code or module, so we need to be sure that this is an actual bug and not just bad data.

Same bug on my views, having aggregations activated.

Patch works for me.

I encountered this in a project after upgrading to PHP 8.1 as well.

I tested it in the standard profile installation (no contrib or custom modules).

Steps to reproduce:

• Enable the Date range module
• Create a date range field (can be cardinality of 1 or unlimited, doesn't matter) on any content type
• Create a node and fill the date field
• Create a view with a page display that lists nodes of the content type
• Add the date field, set format to
• Turn on Aggregation
• Set Aggregation settings on the field to "Minimum"
• Save the view
• Go to the view page and see that the error triggers

Using xdebug, I can see that the $value is a formatted date (eg. 2023-03-09), and I guess it uses NumericField because we use Minimum?
Maybe this is not supported, but I would expect the earliest date to be used when using Minimum.

Updated patch for 10.2

The description and patch in this issue is the same as #3302573.

Sorry, these are actually a little different, but overlapping. This one addresses invalid numeric field values, the related issue is about date strings, which can cause this error because they're an invalid number. There is a patch in there that has this code, however there is also one that tries to fix the dates as well.