Database connection errors should be prefixed in torque renderer #164

Closed
strk opened this Issue Feb 27, 2014 · 2 comments

Projects

None yet

1 participant

@strk

When database is off for any reason, the torque renderer throws an error that only says "Error: connect ECONNREFUSED". It would be nice if it could tell more about the problem, like including the "TorqueRenderer label or something.

It took some time to figure. See CartoDB/Windshaft-cartodb#171

@strk strk added this to the 1.19.2 milestone Feb 27, 2014
@strk strk added the enhancement label Feb 27, 2014
@strk strk referenced this issue in CartoDB/Windshaft-cartodb Feb 27, 2014
Closed

400: Error: connect ECONNREFUSED #171

@strk

I'm wondering if the response should also be a 500 http status rather than a 400, your opinion @javisantana ?

@strk

I'll turn into a 500, the testcase is almost ready

@strk strk pushed a commit that closed this issue Feb 27, 2014
Sandro Santilli Use "TorqueRenderer" prefix for errors generated by it
Closes #164
d9a5c41
@strk strk closed this in d9a5c41 Feb 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment