SearchV2 tests w/o filters expect wrong result order #348

New issue

Closed

opened 2025-12-28 18:16:01 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:16:01 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Feb 27, 2025).

Originally assigned to: @evgeniiz321 on GitHub.

this test run failed on the latest node

Stored objects (in order of creation):

25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA
3S1zXWrNEcMEBNCdmbKbeG1vaHgHcPDyXckBHST7Q9DV
6cuyhTPfoi8gVb1xAt1CZHtHFyTMNeFJerYFuSoGneZw
3yfdPx19qtHkx6Kxz1HBVu1eR6W98Jgwt8wkJY2BMyWy
93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4

and sorted:

93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4
25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA
3S1zXWrNEcMEBNCdmbKbeG1vaHgHcPDyXckBHST7Q9DV
3yfdPx19qtHkx6Kxz1HBVu1eR6W98Jgwt8wkJY2BMyWy
6cuyhTPfoi8gVb1xAt1CZHtHFyTMNeFJerYFuSoGneZw

Expected behavior

CLI outputs objects searched one-by-one in sorted order. If so, test PASSes

Current behaviour But we have

order is correct, but test FAILs with:

AssertionError: invalid ordering in search output
assert '25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA' &gt; '93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4'

Possible solution

i guess expected order can be either:

creation order
string-sorted

both are incorrect. The result must be byte-sorted, i.e. strings must be decoded from base58btc first

filtered suites should also be updated if needed

Originally created by @cthulhu-rider on GitHub (Feb 27, 2025). Originally assigned to: @evgeniiz321 on GitHub. this test [run](https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/2636-1740661204/index.html#suites/1b90fdb5e7b20a803fe835b0d81b2267) failed on the latest [node](https://github.com/nspcc-dev/neofs-node/commit/5e77c4c22caaa5fe5c7f5142df8713360a7c11af) Stored objects (in order of creation): 1. `25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA` 2. `3S1zXWrNEcMEBNCdmbKbeG1vaHgHcPDyXckBHST7Q9DV` 3. `6cuyhTPfoi8gVb1xAt1CZHtHFyTMNeFJerYFuSoGneZw` 4. `3yfdPx19qtHkx6Kxz1HBVu1eR6W98Jgwt8wkJY2BMyWy` 5. `93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4` and sorted: 1. `93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4` 2. `25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA` 3. `3S1zXWrNEcMEBNCdmbKbeG1vaHgHcPDyXckBHST7Q9DV` 4. `3yfdPx19qtHkx6Kxz1HBVu1eR6W98Jgwt8wkJY2BMyWy` 5. `6cuyhTPfoi8gVb1xAt1CZHtHFyTMNeFJerYFuSoGneZw` ## Expected behavior CLI outputs objects searched one-by-one in sorted order. If so, test PASSes ## Current behaviour But we have order is correct, but test FAILs with: ``` AssertionError: invalid ordering in search output assert '25vHFL4xcJUiAogFh9tXngZnNfnswFP9np1YjsaDmozA' > '93eKzH1fPiviQTEvttRwwsUy6NX9mvCXMMD4ASu1me4' ``` ## Possible solution i guess expected order can be either: * creation order * string-sorted both are incorrect. The result must be byte-sorted, i.e. strings must be decoded from base58btc first filtered suites should also be updated if needed

sami

2025-12-28 18:16:01 +00:00

closed this issue
added the
S4

bug

I4

U0
labels

sami commented

2025-12-28 18:16:01 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Feb 27, 2025):

other suite FAILs for the same reason

@cthulhu-rider commented on GitHub (Feb 27, 2025): other [suite](https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/2636-1740661204/index.html#suites/0e3180b9561587482b2f1488d7674deb/97db61dc4e3ca794/) FAILs for the same reason