We noticed that when browsing the Hangfire Dashboard while using the Memory Storage, the jobs pages have an off-by-one error. I compared the source here to the implementation of the SqlServer storage solution and it appears that the method is supposed to be inclusive of both startingFrom and endingAt (i.e., start at 0, end at 9, should give 10 keys).
We noticed that when browsing the Hangfire Dashboard while using the Memory Storage, the jobs pages have an off-by-one error. I compared the source here to the implementation of the SqlServer storage solution and it appears that the method is supposed to be inclusive of both
startingFrom
andendingAt
(i.e., start at 0, end at 9, should give 10 keys).