-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Open
ipfs/boxo
#1071Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/pinningTopic Pinning (local and remote)Topic Pinning (local and remote)
Milestone
Description
Checklist
- My issue is specific & actionable.
- I am not suggesting a protocol enhancement.
- I have searched on the issue tracker for my issue.
Description
The pin add endpoint returns AddPinOutput objects.
When progress=true is specified, an object is set every 500ms containing the number of nodes that have been pinned (Progress field) so far.
I would like to have an additional Size field that additionally contains total size of the DAG pinned so far.
This is necessary to:
- Abort pinning items that are too big
- Being able to inspect the data rate at which an ipfs node can pin.
Can I, or someone work on this?
tux3
Metadata
Metadata
Assignees
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps upeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourshelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featurestatus/readyReady to be workedReady to be workedtopic/pinningTopic Pinning (local and remote)Topic Pinning (local and remote)