Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

notifyrefreshmentsent error

Aperta
  • Qualcosa non va?
#5,402 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
go
Ambito
backend

Direzione di ricerca

Start by following the README in the linked swarm-mobile repository and reproduce with go run main.go, then transfer a large file while collecting Bee logs. The report points to peer disconnections and payment/refresh errors but does not identify a Bee file or test to investigate. Done means explaining and resolving the instability so large uploads or downloads complete without the node crashing or peers dropping unexpectedly.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

on hold
Context

Actively working on to run a Bee node on mobile.
To achieve this, there is a repository which hardly relies on Bee, it is bee-lite. The purpose of this repo is to expose the original Bee API to callable functions instead of using HTTP requests to the locally running Bee node.
In other words, the Android app is implemented in Native Go (using Fyne framework).
swarm-mobile
Achieved running the node in Ultra-light or Light mode.

Tried with the following RPCs it doesn't make any difference:
https://gnosis.publicnode.com
https://xdai.fairdatasociety.org

I have tried with an upgraded node with a funded Chequebook, but that also doesn't make any difference.

Problem

When running 5Mb+ uploads or downloads the log is full of errors like this:
"msg"="notifyrefreshmentsent failed to refresh" "error"="settlement allowance timestamps from peer differed from our measurement by more than 2 seconds"
"msg"="notifyrefreshmentsent failed to refresh" "error"="peer not found"
"msg"="payment failure" "error"="call issue function: connection closed (local): code: 0x0: transport error: sent go away, code: 0"
"msg"="payment failure" "error"="call issue function: stream reset: stream reset: connection closed: EOF"

On some days when the above happens to fast, all the peers get disconnected, and the Bee node crashes during transfer. On other days, the connected peers drop off around 50-60, and the download/upload succeeds.
This is the biggest problem because the node is unstable.

Expected behavior

Node should work normally like on a standard PC.

Actual behavior

Peers are disconnecting, Log is full of errors, and the download/upload sometime works sometime not.

Image [2026-03-17-success-but-nodes-drop-off.log](https://github.com/user-attachments/files/26057304/2026-03-17-success-but-nodes-drop-off.log) [2026-02-27-failure.log](https://github.com/user-attachments/files/26057305/2026-02-27-failure.log) Image
Steps to reproduce

Checkout swarm-mobile follow the Readme to startup the node with the easiest command go run main.go - I'm happy to help anytime with this! - and start a download with a Hash that belongs to a large file

Lingua principale
Go
Stelle
1.5k
Fork
390
Merge medio
2g 11h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ethersphere/bee

Tutte le issue di ethersphere/bee

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.