-
Notifications
You must be signed in to change notification settings - Fork 3
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
spade v0 retrieval worker #33
Conversation
Sample run output:
|
integration/spadev0/util.go
Outdated
"retrieve_size": "1048576", | ||
// todo: specify # of cids to test per layer of the tree TBD | ||
"retrieve_type": string(task.Spade), | ||
"retrieve_size": "1048576", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why the extra space here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's the default gofmt
formatter, which is part of the Go plugin for vscode - it's aligning all of the values to start at the vertical line (ie, because "traverse_depth" is a slightly longer string, it pushes them out an extra space)
In the interest of getting this merged in now, I created this issue for a future improvement: data-preservation-programs/spade#34 |
Closing this PR as it has been moved to the forked SpadeRetrievalBot repo instead. |
closes #32
pkg
to handle the "multi-layer" traversal required for spade CIDs (ex, like this)