Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filc - tracking retrievals and producing CAR files #422

Open
dkkapur opened this issue May 17, 2022 · 1 comment
Open

filc - tracking retrievals and producing CAR files #422

dkkapur opened this issue May 17, 2022 · 1 comment
Labels
P1 P1 Issue workstream/repsys Issue blocks Reputation System MVP workstream/slingshot Issue is blocking for bulk Slingshot retrievals

Comments

@dkkapur
Copy link
Collaborator

dkkapur commented May 17, 2022

Following up on conversations happening on the data-programs/evergreen front and at the bedrock hack week, here's an issue to track the improvements we should make to filc (filclient lib).

Overarching motivation:

  • automate retrieval attempt tracking so we can identify where things are failing
  • provide actionable failure reports to lotus-dev and bedrock

Requirements:

  • clients should be able to use filc to retrieve CIDs as CAR file
  • instrument the retrieval flow from filc to produce DEBUG logs for the full lifecycle of a retrieval attempt (from initial dial to CAR output to disc or failure outcome with failure reasons)
@dkkapur dkkapur added workstream/slingshot Issue is blocking for bulk Slingshot retrievals workstream/repsys Issue blocks Reputation System MVP P1 P1 Issue labels May 17, 2022
@dkkapur
Copy link
Collaborator Author

dkkapur commented May 18, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 P1 Issue workstream/repsys Issue blocks Reputation System MVP workstream/slingshot Issue is blocking for bulk Slingshot retrievals
Projects
Support Data Programs
Awaiting triage
Development

No branches or pull requests

1 participant