-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: check if reserve is configured #4837
Conversation
this is not a real solution, i think. we need to first understand why the reserve is nil. Chances are this is a light node and it was unable to find a peer to push the chunk to so it tried storing it. In that case, we need to plug that hole, where a light node should not try to store a chunk in the above scenario. but this is one theory. we need to ask the issue creator the config options he was running with before hastily jumping onto a solution. |
I also got this from this failed beekeeper test
Config
The reverse is not configured because Line 730 in 0e42d83
But the pushsync only uses Line 953 in 0e42d83
Lines 401 to 406 in 0e42d83
So initializing pushsync consistently with |
c5ceef1
to
0d78b93
Compare
does that mean that an upload was attempted from a bootnode? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very good finding. But I think that when I investigated the issue, actually the reserve seamed not to be nil, else it would have crashed even earlier. Please can you confirm that the reserve is not used in earlier places?
yes. See https://github.com/ethersphere/bee/actions/runs/11434065514/job/31807011143
I don't see any other place. The stack trace indicates that the receiver is nil.
|
Checklist
Description
Check if reserve is configured before attempting to put chunk
Related Issue (Optional)
#4829