GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
In the Raven 2.0.3 docs, there is a parameter called 'timeout'. But when I tried to set this value, the raven client is not accepting it.
I am setting the timeout like this.
client = Client(
And if I look at raven/base.py, I see this which seems to suggest that the timeout parameter cannot be set in the above config.
if kwargs.get('timeout') is not None:
warnings.warn('The ``timeout`` option no longer does anything. Pass the option to your transport instead.')
And I tried to pass this config in the transport (I did something like this on the dsn) and it does not work as well...
But if I change raven/conf/defaults.py (TIMEOUT), raven accepts this change.
my understanding of the code is that if you add ?timeout=10 on the server url in the example above it will work.
the problem is when using raven with Django. RAVEN_CONFIG['timeout'] is ignored and if you add the timeout to the dsn as above, that gets stripped out by the time it ends up in the servers list and thus the url given to TransportRegistry:get_transport().
scheme = ['http', 'https']
def __init__(self, parsed_url, timeout=defaults.TIMEOUT):
In raven/transport/base.py, transport object take defaults.TIMEOUT as default function parameter. Change defaults.TIMEOUT will not effect HTTPTransport().timeout. There is no way in user's code to change the timeout.
Consider the following code:
TIMEOUT = 1
foo.TIMEOUT = 2
result will be
This issue will be followed in #253 as the timeout parameter seems broken at the moment.