You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug relates to #2008.
The fix applied in #2018 didn't resolve the issue completely.
When requesting the catalog using limit and offset queryparams, the number of contractOffers returned does not correspond to the expected.
Steps to Reproduce
Test scenario:
2 Contract definitions with asset selector criteria refering to 50 assets each (Expected total of 100 offers).
Consumer requests the catalog from provider using different limit and offset.
Expected Behavior
Behaviour a)
limit=52
offset=0
expected offers: 52
Behaviour b)
limit=2
offset=49
expected offers: 2
Observed Behavior
Behaviour a)
observed offers: 100
behaviour b)
observed offers: 3
Used version
0.0.1-20230213-SNAPSHOT
Possible Implementation
On ContractOfferResolverImpl.queryContractOffers() when skip is a value under 0, limit for next iteration should be the result of the current limit minus the skip.
The text was updated successfully, but these errors were encountered:
Bug Report
Describe the Bug
This bug relates to #2008.
The fix applied in #2018 didn't resolve the issue completely.
When requesting the catalog using
limit
andoffset
queryparams, the number of contractOffers returned does not correspond to the expected.Steps to Reproduce
Test scenario:
limit
andoffset
.Expected Behavior
Behaviour a)
limit=52
offset=0
expected offers: 52
Behaviour b)
limit=2
offset=49
expected offers: 2
Observed Behavior
Behaviour a)
observed offers: 100
behaviour b)
observed offers: 3
Used version
0.0.1-20230213-SNAPSHOT
Possible Implementation
On
ContractOfferResolverImpl.queryContractOffers()
whenskip
is a value under 0,limit
for next iteration should be the result of the currentlimit
minus theskip
.The text was updated successfully, but these errors were encountered: