You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.
Context
I'm testing out GSOC functionality which uses fdp-play for environment (5 nodes network).
It implies that I'm pushing several chunks under one SOC address. nevertheless, I do not think it causes the problem.
Based on Bee 2.2
Related logs
Performed 7 POST soc chunk requests in the same time.
If I call POST SOC sequentially one-by-one everything works as expected,
but if I do this parallel, some chunks will not be pushed to the network still returns with successful 201 response.
From the logs, it can be seen by searching the term chunk pushed how many successful pushes have happened
and ,"status"=201 is the key to show successful API responses.
Expected behavior
All chunks pushed to the network (7 out of 7)
Actual behavior
Not all chunks have been pushed to the network (3-4 out of 7)
Moreover, it does not show any error about the push failure from the API side.
Steps to reproduce
Build GSOC subscribe branch with FDP Play then run test of GSOC: npm run test -- -t 'send messages with different postage batches parallel'.
npm run test -- -t 'send message with different postage batches sequentially' shows that it works sequentially.
Possible solution
The text was updated successfully, but these errors were encountered:
Context
I'm testing out GSOC functionality which uses fdp-play for environment (5 nodes network).
It implies that I'm pushing several chunks under one SOC address. nevertheless, I do not think it causes the problem.
Based on Bee 2.2
Related logs
Performed 7 POST soc chunk requests in the same time.
Summary
If I call POST SOC sequentially one-by-one everything works as expected,
but if I do this parallel, some chunks will not be pushed to the network still returns with successful 201 response.
From the logs, it can be seen by searching the term
chunk pushed
how many successful pushes have happenedand ,
"status"=201
is the key to show successful API responses.Expected behavior
All chunks pushed to the network (7 out of 7)
Actual behavior
Not all chunks have been pushed to the network (3-4 out of 7)
Moreover, it does not show any error about the push failure from the API side.
Steps to reproduce
Build GSOC subscribe branch with FDP Play then run test of GSOC:
npm run test -- -t 'send messages with different postage batches parallel'
.npm run test -- -t 'send message with different postage batches sequentially'
shows that it works sequentially.Possible solution
The text was updated successfully, but these errors were encountered: