Bug #1410
Python socket transport swallows missing converter errors silently so that clients can end up blocking endlessly
Status: | New | Start date: | 02/13/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Python | |||
Target version: | rsb-0.18 |
Description
The current implementation of the socket transport only defines the following error hook on the connection:
connection.errorHook = lambda exception: self.removeConnection(connection)
This doesn't notify clients in any error case, nor does it print a warning message (without specifically configured logging) or crashes the program. This is the warning code:
self.__logger.warn('Receive error: %s', e)
At least:
- use a more serious warning level
- use a method signature that prints a complete exception stacktrace
Related issues
History
#1 Updated by J. Moringen about 11 years ago
- Target version changed from rsb-0.9 to rsb-0.10
#2 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#3 Updated by J. Moringen over 9 years ago
- Target version changed from rsb-0.11 to rsb-0.12
#4 Updated by J. Moringen almost 9 years ago
- Target version changed from rsb-0.12 to rsb-0.13
#5 Updated by J. Moringen about 8 years ago
- Target version changed from rsb-0.13 to rsb-0.14
#6 Updated by J. Moringen almost 8 years ago
- Target version changed from rsb-0.14 to rsb-0.15
#7 Updated by J. Moringen over 7 years ago
- Target version changed from rsb-0.15 to rsb-0.16
#8 Updated by J. Moringen about 7 years ago
- Target version changed from rsb-0.16 to rsb-0.17
#9 Updated by J. Moringen over 6 years ago
- Target version changed from rsb-0.17 to rsb-0.18