filecoin-project/boost

Graphsync retrievals canceled by client show as Failed in Boost UI

Open

#1,767 opened on Oct 20, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (77 forks)github user discovery
good first issuekind/enhancement

Repository metrics

Stars
 (121 stars)
PR merge metrics
 (PR metrics pending)

Description

Checklist

  • This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.

Boost component

  • boost daemon - storage providers
  • boost client
  • boost UI
  • boost data-transfer
  • boost index-provider
  • Other

Improvement Suggestion

Graphsync retrievals that are cancelled by boost client result in retrieval marked as Failed in the boostd UI:

We should detect errors better and mark these retrievals as canceled by client, and not really failed.

Contributor guide