FYI there is a similar ticket for R client
I have tried the following test three times on belltown and each time it has failed with the same error
--> 612 s = self.fp.read(amt)
613 if not s and amt:
614 # Ideally, we would raise IncompleteRead if the content-length
/home/apratap/softwares/anaconda/lib/python2.7/socket.pyc in read(self, size)
382 # fragmentation issues on many platforms.
--> 384 data = self._sock.recv(left)
385 except error, e:
386 if e.args == EINTR:
/home/apratap/softwares/anaconda/lib/python2.7/ssl.pyc in recv(self, buflen, flags)
732 "non-zero flags not allowed in calls to recv() on %s" %
--> 734 return self.read(buflen)
736 return self._sock.recv(buflen, flags)
/home/apratap/softwares/anaconda/lib/python2.7/ssl.pyc in read(self, len, buffer)
619 v = self._sslobj.read(len, buffer)
--> 621 v = self._sslobj.read(len or 1024)
622 return v
623 except SSLError as x:
error: [Errno 104] Connection reset by peer
I don't know about the network conditions but suspect that they are very good as they are downloading multiple 1 TB files. The files are stored in S3 through a custom storage location. That is, the bucket has given permission to Synapse (not ExternalObjectStore filehandles).
Changed from Critical to Major. let me know if you disagree.
I believe that this is request package error. The solution is updating the request package's dependencies:
Related to SYNPY-776.
, this issue is actually nothing to fix in the client, since it's the requests package dependencies. The fix for the end users is to update their requests package. Since we didn't add anything to the release 1.9.0 for this issue, its validation shouldn't hold up version 1.9.0 release.