Bee seems to return index 0 for sequential feeds
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go
- Domain
- backend, distributed-systems
Research direction
Reproduce the behavior with a sequential feed containing at least 2–3 updates, then open its address through the /bzz/ endpoint. Trace the sequential feed lookup path and compare the selected update with the expected latest update. Done means the endpoint returns the latest feed update consistently; no specific file or test is named in the issue.
Written by the indexing model from the issue text.
Description
⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.
Context
While testing feeds the following behaviour was observed: bee returns first update instead of latest update for sequencial feeds
Summary
Sequential feed lookup seems to have regressed to returning first available feed update
Expected behavior
Lookup to find latest update
Actual behavior
Lookup returning with first update
Steps to reproduce
Create feed with at least 2-3 updates
Open feed address through /bzz/ endpoint
First update is displayed instead of latest
Possible solution
Sanity check lookup logic is intact
- 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
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
install-path local lint proofs will exit 5 on roster-less machines once #3263 release is pinnedOpenraised-by:reviewer
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
medici-finance/assay#3333 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
onurbaydas/VirtoMir#9 ·
-
Add --version flagOpenenhancement good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
syncronix-labs/aegora#12 ·
-
auto-fixable pkg:api
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tphakala/birdnet-go#4650 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day