Can't pin large files uploaded with chunks
Maintainers usually reply within 2 days
@acha-bill is already working on this.
Since Apr 3, 2025.
Assessment
This issue has not been assessed yet.
Description
Context
Bee 2.2.0
Summary
Even using tags to upload with sessions, is not possible to pin large files providing all the chunks.
Expected behavior
I expect when using tags that chunks are preserved on node until the tag is released. A pinning request on root hash with tag alive, and all chunks uploaded, should succeed.
Actual behavior
Instead, also with tag alive, is possible that successive pinning request will fail returning error 404, and making pinning with chunks actual impossible.
Steps to reproduce
Try to upload a large file with chunks on a connected node, using tags. A successive request to pin the root may fail with 404 error code.
Possible solution
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 390
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ethersphere/bee
-
Chequebook deployment uses a fixed 175,000 gas limit; it needs about 630,000 under Glamsterdam (live on Sepolia since 2026-10-06)Possibly taken @sbackend123 claimed this 9 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ethersphere/bee#5650 · 1 assignee ·
Maintainers usually reply within 2 days
-
Add a transaction inbox for outbound chain transactionsPossibly taken @sbackend123 claimed this 3 days ago. Openseen
Difficulty 5/5 Over a week Newbie friendliness 35/100
ethersphere/bee#5660 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ethersphere/bee#5659 ·
Maintainers usually reply within 2 days
-
accepted seen
Difficulty 4/5 3-5 days Newbie friendliness 40/100
ethersphere/bee#5648 · 1 comment ·
Maintainers usually reply within 2 days
-
pusher: chunksWorker deadlocks on a deferred chunk that fails IdentityAddress (send on nil op.Err), halting all push-syncPossibly taken @sbackend123 claimed this 11 days ago. Openseen
Difficulty 3/5 1-2 days Newbie friendliness 75/100
ethersphere/bee#5641 · 1 assignee ·
Maintainers usually reply within 2 days
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
wakatime/wakatime-cli#1649 ·
Maintainers usually reply within 1 day
-
PathBuffer.Pop corrupts later error locations when a key contains "." or "["Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
danielgtaylor/huma#1135 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stacklok/toolhive-catalog#1734 ·
Maintainers usually reply within 1 day
-
documentation priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yeixio/toskar-core#697 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
keyxmakerx/Chronicle#1532 ·
Maintainers usually reply within 1 day