handle incomplete search result #125

Closed
opened 2025-12-28 18:00:15 +00:00 by sami · 3 comments
Owner

Originally created by @532910 on GitHub (Nov 5, 2025).

Originally assigned to: @smallhive on GitHub.

neofs-rest-gw: error        handlers/api.go:144        could not search for objects
{
  "handler": "NewGetByAttribute",
  "containerID": "5Feinb2PaGFqdzviYfodCRMKd4j49Rtey3rSGqGhX8wn",
  "attrKey": "FilePath",
  "attrVal": "index.html",
  "error": "search: status: code = 1 message = last error: all 03933279423bf3504b61f76912790a566d99929eb047f30c8699f8e49a34ab07f7 endpoints failed, first error: /dns4/minerva.nspcc.ru/tcp/8080: send request over gRPC: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 51.77.119.31:8080: i/o timeout\""
}
Originally created by @532910 on GitHub (Nov 5, 2025). Originally assigned to: @smallhive on GitHub. ``` neofs-rest-gw: error handlers/api.go:144 could not search for objects ``` ```Json { "handler": "NewGetByAttribute", "containerID": "5Feinb2PaGFqdzviYfodCRMKd4j49Rtey3rSGqGhX8wn", "attrKey": "FilePath", "attrVal": "index.html", "error": "search: status: code = 1 message = last error: all 03933279423bf3504b61f76912790a566d99929eb047f30c8699f8e49a34ab07f7 endpoints failed, first error: /dns4/minerva.nspcc.ru/tcp/8080: send request over gRPC: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 51.77.119.31:8080: i/o timeout\"" } ```
sami 2025-12-28 18:00:15 +00:00
  • closed this issue
  • added the
    bug
    S4
    I4
    U1
    labels
Author
Owner

@roman-khimov commented on GitHub (Nov 5, 2025):

Implicit searches should accept whatever they received, they're "best effort" by design. Search API should report this status to users ("incomplete" flag probably, HTTP codes don't have anything appropriate, 206 is range-only, 203 is for a different scenario as well).

@roman-khimov commented on GitHub (Nov 5, 2025): Implicit searches should accept whatever they received, they're "best effort" by design. Search API should report this status to users ("incomplete" flag probably, HTTP codes don't have anything appropriate, 206 is range-only, 203 is for a different scenario as well).
Author
Owner

@532910 commented on GitHub (Nov 14, 2025):

not fixed, please reopen:
neofs-rest-gw: error handlers/api.go:144 could not search for objects {"handler": "NewGetByAttribute", "containerID": "4NNxPxCHiNv2CJW3526sct7Y5agTXUZ3BE2u3yVwx4eK", "attrKey": "FilePath", "attrVal": "index.html", "error": "search: rpc failure: rpc error: code = Canceled desc = context canceled"}

@532910 commented on GitHub (Nov 14, 2025): not fixed, please reopen: neofs-rest-gw: error handlers/api.go:144 could not search for objects {"handler": "NewGetByAttribute", "containerID": "4NNxPxCHiNv2CJW3526sct7Y5agTXUZ3BE2u3yVwx4eK", "attrKey": "FilePath", "attrVal": "index.html", "error": "search: rpc failure: rpc error: code = Canceled desc = context canceled"}
Author
Owner

@roman-khimov commented on GitHub (Nov 14, 2025):

It's a completely different issue.

@roman-khimov commented on GitHub (Nov 14, 2025): It's a completely different issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-rest-gw#125
No description provided.