First() and Last() methods break in Sqlite provider

[AdamIzon]

When I call IQueryable.First() or IQueryable.Last(), I get the exception [SQLite Error 1: 'near "FETCH": syntax error'].
When I look at the debug view on the IQueryable object before calling First() or Last() there is no "FETCH" in the SQL query, so First() and Last() must be adding this.

When I remove this package from my project this behaviour goes away.

[AdamIzon]

Example:

For the given LINQ:

var blockades = _dbContext.Blockade;
var testQuery = blockades.Select(b => EF.Functions.RowNumber(EF.Functions.Over().OrderBy((long)b.BlockadeStartIndex)));
var average = testQuery.First();

The SQL code being generated is

SELECT ROW_NUMBER() OVER(ORDER BY CAST("b"."BlockadeStartIndex" AS INTEGER))
FROM "Blockade" AS "b"
WHERE "b"."RecordingId" = @__recording_Id_0
ORDER BY CAST("b"."BlockadeStartIndex" AS INTEGER)
FETCH FIRST 1 ROWS ONLY

but to clarify, this breaks any call to IQueryable.First()... not just queries containing window functions

[LecksC]

Can confirm anything as simple as dbContext.MyTable.FirstOrDefault() gives SQLite Error 1: 'near "FETCH": syntax error'. As soon as I add .UseWindowFunctions() it changes from:

SELECT "m"."Id"
FROM "MyTable" AS "m"
LIMIT 1

to

SELECT "m"."Id"
FROM "MyTable" AS "m"
    FETCH FIRST 1 ROWS ONLY

The latter of which isn't valid.

I tried versions from 8.0.1-preview4 to 8.0.21-beta and several versions in between (including the non preview/beta versions)

[TheTedder]

This should be fixed now. I used the following code to confirm (using the test data in the repo).

var firstDbRow = DbContext.TestRows.First();
var expected = TestRows.First();
Assert.Equal(expected, firstDbRow, TestRowEqualityComparer.Default);