Not sure if this is still the same bug, but I got this today around "May 30, 2022 at 13:56 CEST"

Remainder of query was not run (used 10.01 seconds so far)


Found 0 nodes roughly between 2022-05-30 and 0 (searched 567.28% of DB). 


where any text contains all of "debugger", "ornament"

Date:	Author/owner:	Title:	Node type:

Press >NEXT< to continue searching remaining 304.68% of DB.
Please be patient after submitting your search.

Link to preload this search: ?node_id=3989;BIT=debugger%20ornament

(emphasize added)

Please note the 0 too, there seems to be a date problem in edge cases causing such high percentages ...

EDIT

Couldn't reproduce it now, probably dependent on other side effects.

update

Kind of a Heisenbug, if you run the exact same search, you'll end up in this new node now.

You need an "impossible" query to force a "Found 0 nodes" response.

update

My best guess, this happens only if the 10sec timeout ends above the giant jump from 2019, i.e. the server must be busy and this problem will happen more and more often in the future.