REST API Pagination Does not work as expected

[lbajsarowicz]

Preconditions (*)

1. Magento 2.3.4
2. REST API Call

Steps to reproduce (*)

1. Fixture with 3 orders
2. Request with page_size = 1 and current_page = 99

Expected result (*)

1. total_count returns 3
2. items returns empty array OR OutOfRangeException

Actual result (*)

1. total_count is 3
2. items returns repeated last page of results

Kudos for

@ihor-sviziev , @Vinai , @nuzil for discussion at #appdesign channel about this issue.

[m2-assistant]

Hi @lbajsarowicz. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@lbajsarowicz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[lbajsarowicz]

I'm going to address the issue with data described with dataProvider:

magento2/dev/tests/api-functional/testsuite/Magento/Catalog/Api/ProductRepositoryInterfaceTest.php

Lines 1147 to 1176 in 6771122

	/**
	* Keep in mind: Fixture contains 5 products
	*
	* @return array
	*/
	public function productPaginationDataProvider()
	{
	return [
	'expect-all-items' => [
	'pageSize' => 10,
	'currentPage' => 1,
	'expectedCount' => 5
	],
	'expect-page=size-items' => [
	'pageSize' => 2,
	'currentPage' => 1,
	'expectedCount' => 2
	],
	'expect-less-than-pagesize-elements' => [
	'pageSize' => 3,
	'currentPage' => 2,
	'expectedCount' => 2
	],
	'expect-no-items' => [
	'pageSize' => 100,
	'currentPage' => 99,
	'expectedCount' => 0
	]
	];
	}

[lbajsarowicz]

The source of the issue is located in:

magento2/lib/internal/Magento/Framework/Data/Collection.php

Lines 240 to 249 in 09de30c

	public function getCurPage($displacement = 0)
	{
	if ($this->_curPage + $displacement < 1) {
	return 1;
	} elseif ($this->_curPage + $displacement > $this->getLastPageNumber()) {
	return $this->getLastPageNumber();
	} else {
	return $this->_curPage + $displacement;
	}
	}

Although $this->_curPage is overwritten by the

    if ($this->_curPage + $displacement > $this->getLastPageNumber()) {
        return $this->getLastPageNumber();
    }

That is not passed back to all APIs. There are two options, actually:

1. Remove above-mentioned mechanism to return no values when we reached the last page.
2. Pass the information about overwritten currentPage to API

I choose (1) as for me it's more obvious.

[magento-engcom-team]

Hi @lbajsarowicz. Thank you for your report.
The issue has been fixed in #26988 by @lbajsarowicz in 2.4-develop branch
Related commit(s):

• a6f76f346596a80243596079f90fe0b78f7dc744
• b254764a3c654b8ed48c36086864478bfb6c953e
• 11567f6004dbc6819c19bd42e95915dfbf3a046f
• 6771122e05e1c49fc4f83409bd6fd18ffaaf0951
• e001493a7877e5f00a53ae1d34a98039b8e0313e
• ecb3a8d393854ab1ab0543f541fd64d5c1941015
• 015c5fcc53b96efa460c05ec4047006fbf68e753
• 18e43a8df8581586b7ba3110e3feebcd6e1910d7
• 9d0ae13e97e6403766fe7eba7cde9946095866e5
• 2439e17df3ec42440f25efad2e2b2a7d3be0de5e
• 14ea3358e08c26403d1a322f270daa55a4d2e033
• 0fe9cf207bc902350d5ebfc4b5a665679db6edc0
• dab0cda47e62d8b519fcac798f9221066615d7ec
• c403c52ac09373dded105ec0c5d08772730df7b6
• d7cdd7bf6f397119c83814d412ed02f8702cb7fb
• 05f1a2b01bbc085b3b9db9db1217c317c1f1de42
• f25de7bffe498d35d05064814cb3671a91208c09
• 51a18f657bbd17155792147dd1436faa377482e6
• 0bae5d5420efb58ac0be0abe317d01c3931e49c4
• 1e7082dcd43f8556e951b5b1112a14a6f29aefd7
• f5aa61dfeec3a96be19948d54eaeb701fcfc7231
• e8d3b78b81d7041d1952d4a8150a1970950a7147
• 6c171ce75fdadddc993463a3175918ef1d2158d7
• 8c9189f8ab4dcfb82cd1c5b54ea8528aab8d8779
• 68cf64d2d9fb7c11b6f268ef159ab56a7db906c5
• 0db92206a634c5453780e6b9aef9fd0922f9874d
• c44bbf5d269883a570c60304f90d8d5946ae6971
• 84fdc7a643f2039149b081dc13572a3b80e63b0b
• 162eb14bdc3acd8a983a3633d11f2987692c7186
• 11c3eeaf6d2cd5d096aac2952eb145eaf4a2ba49
• 986a4ef2b1260c5c445b83f4a678f6c6af019b1d
• 80cb06e283a030ac3872ca46c4be17104dd87e83
• db71c464b0c803775c11c4988c47c4f929e32131
• e105152c438dfed86918f40ec4da0f89dc537436
• bd5c98ea3e094233b9a29f61a5d9082de6dd2d88

The fix will be available with the upcoming 2.4.0 release.