Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tagging does not work on direct BZZ upload

Open
#5,096 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@rose2221 is already working on this.

Since Jun 23, 2025.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
go
Domain
api, backend

Research direction

Start by tracing the /bzz upload handling for swarm-deferred-upload: false and how it applies the supplied swarm-tag; compare that flow with tag progress updates for deferred uploads. The report includes reproducible curl steps and the expected chunk-count updates, but names no source files or tests. Done means the tag reflects upload progress and final chunk counts for a direct upload.

Written by the indexing model from the issue text.

Description

good first issue

⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.

Context

Bee 2.5

Summary

When attempting to upload data to the /bzz endpoint using a pre-generated tag (via the Tag API), the tagging functionality does not work if the swarm-deferred-upload: false header is set (for direct uploads).

Expected behavior

The tag should track the upload progress and reflect the correct chunk counts as the upload proceeds and completes.

Actual behavior

The tag does not update the upload status when swarm-deferred-upload: false is set.

Steps to reproduce
  1. Generate a tag

curl -X POST http://localhost:1633/tags

Note the uid from the response.

  1. Attempt to upload a file with direct upload and tagging
curl -X POST \
  -H "swarm-deferred-upload: false" \
  -H "Content-Type: application/x-tar" \
  -H "swarm-postage-batch-id: <BATCH_ID>" \
  -H "swarm-tag: <TAG_ID>" \
  --data-binary @my_data.tar \
  http://localhost:1633/bzz
  1. Check the tag status

curl http://localhost:1633/tags/<TAG_ID>

Dominant language
Go
Stars
1.5k
Forks
390
Avg merge
2d 11h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ethersphere/bee

All issues in ethersphere/bee

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.