Message2920
We frequently get emails from roundup about broken pipes in the ExportCSVAction, such as
Traceback (most recent call last):
File "/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/client.py", line 265, in inner_main
html = self.handle_action()
File "/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/client.py", line 841, in handle_action
return action_klass(self).execute()
File "/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/actions.py", line 39, in execute
return self.handle()
File "/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/actions.py", line 994, in handle
writer.writerow([str(klass.get(itemid, col)) for col in columns])
File "socket.py", line 248, in write
self.flush()
File "socket.py", line 235, in flush
self._sock.sendall(buffer)
error: (32, 'Broken pipe')
The attached patch prevents these errors, ignoring them the same way other write failures to the socket get ignored. |
|
Date |
User |
Action |
Args |
2009-02-03 14:23:17 | admin | link | issue1911449 messages |
2009-02-03 14:23:17 | admin | create | |
|