search

storj-archived / storjshare-gui

Development on pause
https://storj.io/share.html
GNU Affero General Public License v3.0
460 stars 100 forks source link

Can\'t set headers after they are sent #694

Closed MeijeSibbel closed 5 years ago

MeijeSibbel commented 7 years ago

Versions

Replace the values below with your own:

Expected Behavior

Please describe the program's expected behavior.

Actual Behavior

Please describe the program's actual behavior. Please include any stack traces or log output in the back ticks below.

http_outgoing.js:367
throw new Error('Can\'t set headers after they are sent.');
^

Error: Can't set headers after they are sent.
at ServerResponse.setHeader (_http_outgoing.js:367:11)
at ServerResponse.format (C:\Program Files\Storj Share\resources\app\node_modules\restify\lib\response.js:147:10)
at ServerResponse.send (C:\Program Files\Storj Share\resources\app\node_modules\restify\lib\response.js:340:14)
at ReadableFileStream._handleReadFailure (C:\Program Files\Storj Share\resources\app\node_modules\storj-lib\lib\network\shard-server.js:257:11)
at emitOne (events.js:96:13)
at ReadableFileStream.emit (events.js:188:7)
at _sBucket._db.get (C:\Program Files\Storj Share\resources\app\node_modules\kfs\lib\read-stream.js:57:23)

Steps to Reproduce

Please include the steps the reproduce the issue, numbered below. Include as much detail as possible.

  1. ...
  2. ...
  3. ...

Screenshots (Optional)

If the error is graphical in nature it is helpful to provide a screenshot.

xyphosbz commented 7 years ago

GUI 6.4.0 Daemon 3.5.5 Core 6.8.0 Protocol 1.1.0

Operating System:

System Manufacturer: ASUSTeK Computer Inc. Processor: Intel(R) Pentium(R) CPU B960 @ 2.20GHz (2 CPUs), ~2.2GHz Memory: 6144MB RAM

Expected Behavior

The program should not restart by itself when downloading data to be stored (shards).

Log Files: logs.zip

Storage Location, network drive: image

Actual Behavior

_http_outgoing.js:367 throw new Error('Can\'t set headers after they are sent.'); ^

Error: Can't set headers after they are sent. at ServerResponse.setHeader (_http_outgoing.js:367:11) at ServerResponse.format (C:\Program Files\Storj Share\resources\app\node_modules\restify\lib\response.js:147:10) at ServerResponse.send (C:\Program Files\Storj Share\resources\app\node_modules\restify\lib\response.js:340:14) at ReadableFileStream._handleReadFailure (C:\Program Files\Storj Share\resources\app\node_modules\storj-lib\lib\network\shard-server.js:257:11) at emitOne (events.js:96:13) at ReadableFileStream.emit (events.js:188:7) at _sBucket._db.get (C:\Program Files\Storj Share\resources\app\node_modules\kfs\lib\read-stream.js:57:23)

Steps to Reproduce

I have a network drive in my local network which is accessed via the program netdrive. http://www.netdrive.net/ Program Version: 2.6.15

I have full read, write permission on the share, I go through the normal setup procedure of storjshare and it starts without any problems. The issue above occurs when my node starts to get data and downloads it. I have a 4Mbps internet connection. During the process of downloading the error comes up and the node restarts.

ne0ark commented 7 years ago

It doesn't work well with netdrive or any mounted drive. Too much lag introduced.

RichardLitt commented 5 years ago

👋 Hey! Thanks for this contribution. Apologies for the delay in responding!

We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.

As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!