@chmst can you please test?

This does not work. It results in a notice in view.html.php, where an array is expected, empty or not..
An empty result in articles is quite normal.
The related issue was probably caused by an inconxistency in the database of my repo. After installing the whole new with a fresh database, theis issue was solved.

It results in a notice in view.html.php, where an array is expected, empty or not..

The view needs to account for this return type too. Folks, error handling is simple; you should not be writing code assuming that things will never have errors and things will always work as expected and you can't tell people the fix to running into these errors is to drop your database and reinstall everything. Error handling is not a new programming concept, but the fact that Joomla has next to none of it is quite embarrassing.

I agree with @chmst
Finding zero records is not an error to return false
An empty array should be returned.

Regarding the error handling in case that this method return false on real errors, i agree with @mbabker, view.html.php should be patched too (in some other PR along with other files ?)

Finding 0 records is not the error, getItems() in that case should be returning an empty array (because of type coercion with PHP the if check probably needs to be if ($items === false)). The intent here is to handle the case when getItems() DOES reach an error and returns boolean false instead of an array. And no, returning an empty array in the error case is not a proper fix.

patched the view

Well, as far as i can quickly see, it's possible to get an empty array from getTransitions. That gives a 500 error however because the view checks for falsy instead of false.

@alikon can you patch the comment from @euismod2336 please

@wilsonge @euismod2336 not sure to understand can you elaborate and/or add suggestion, pr is open

Done and thanks :)