26.4.2 "Non-existent edge type" bug when used with ranges

[DicconTownsXophea]

I've noticed a change between 26.3.2 and 26.4.2 - if you query a non-existent edge type with a range in 26.4.2 you get an error:

SELECT bothE("NonExistentEdge")[0...25] FROM #54:402 

raises:

Type with name 'NonExistentEdge' was not found

Removing the range prevents the error:

SELECT bothE("NonExistentEdge") FROM #54:402 

returns:

[]

In 26.3.2 both examples return an empty array (the preferred outcome)

[lvca]

Reproduced.

[lvca]

Fixed