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.
this issue is happening again today. nobody can create any new nodes.
i just noticed on storjstat that before the 12/13 of october the lowest response time reported was 295, but after the 13th of october the lowest reported RT is always 0. so maybe look into what changed between the 11th and the 13th of october.
i suspect there are currently hundreds of nodes with this problem and the users dont even know their nodes arent working (theres at least some otherwise storjstat wouldnt report lowest RT as 0)
many users will start farming run into this issue and even after months not get anything and leave angry
Package Versions
Replace the values below using the output from
npm list storj-bridge
.Replace the values below using the output from
node --version
.Expected Behavior
Please describe the program's expected behavior. Include an example of your
usage code in the back ticks below if applicable.
Actual Behavior
Please describe the program's actual behavior. Please include any stack traces
or log output in the back ticks below.
We have a lot of new farmer with responseTime null. The bridge will never send them any ALLOC messages: https://github.com/Storj/bridge/blob/3134e47d0fd1ffed3591498c0af41a73faa2656d/lib/server/routes/frames.js#L172
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
The text was updated successfully, but these errors were encountered: