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
{{ message }}
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
Replace the values below using the output from node --version.
v6.11.5
Test Setup
As renter I try to upload a shard. The bridge will send out a group of ALLOC requests and give me one farmer for my shard upload.
I will not upload and ask the bridge again for the same shard hash. The bridge will use the queued ALLOC responses.
Repeat that to get a list of farmer that are qualified for the shard upload.
Expected Behavior
Please describe the program's expected behavior. Include an example of your
usage code in the back ticks below if applicable.
I would expect to see random farmer on the list. The ALLOC request is working correct. A few farmer with nodeIDs close to the generated random
I would expect to see random farmer on the list.
The ALLOC request is working correct. I can see a group of ~20 low responseTime farmer plus a few high responseTime farmer.
Actual Behavior
Please describe the program's actual behavior. Please include any stack traces
or log output in the back ticks below.
The bridge is still using the fastest response for the shard upload. The farmer list is ordered by responseTime.
Package Versions
Replace the values below using the output from
npm list storj-bridge
.Replace the values below using the output from
node --version
.Test Setup
As renter I try to upload a shard. The bridge will send out a group of ALLOC requests and give me one farmer for my shard upload.
I will not upload and ask the bridge again for the same shard hash. The bridge will use the queued ALLOC responses.
Repeat that to get a list of farmer that are qualified for the shard upload.
Expected Behavior
Please describe the program's expected behavior. Include an example of your
usage code in the back ticks below if applicable.
I would expect to see random farmer on the list. The ALLOC request is working correct. A few farmer with nodeIDs close to the generated random
Actual Behavior
Please describe the program's actual behavior. Please include any stack traces
or log output in the back ticks below.
The bridge is still using the fastest response for the shard upload. The farmer list is ordered by responseTime.
Shard hash | farmer nodeID | farmer responseTime (from bride contact list)
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
Complete list
Daten.csv.txt
The text was updated successfully, but these errors were encountered: