Title ProgrammingError while deleting patch set
Priority bug Status resolved
Superseder Nosy List Retro, berker.peksag, ezio.melotti, loewis, tshepang
Assigned To Topics

Created on 2012-01-23.20:23:06 by Retro, last changed 2018-06-12.18:30:57 by berker.peksag.

msg2369 (view) Author: Retro Date: 2012-01-23.20:23:05
I wanted to delete a patch set that I have uploaded to a Python issue reporting portal @, but I got a

"ProgrammingError at /review/13816/patchset/4039/delete
schema "datetime" does not exist"

and got all the Django nitty-gritty info about the Python server. This is not good because someone can misuse that information. Please fix this. The "DEBUG = True" is set and so all the details about the Python server is out on the open. Better change that to "DEBUG = False" and let the user get a standard 500 error page instead.

It says at the bottom: "You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 500 page."

And, of course, fix the ProgrammingError so that the option "Delete Patch Set" would work. :)
msg2370 (view) Author: ezio.melotti Date: 2012-01-23.21:09:31
I now set DEBUG = False in gae2django/ and rietveld/
msg2371 (view) Author: Retro Date: 2012-01-23.21:56:45
Good. But don't forget to fix the bug as well.
msg3491 (view) Author: berker.peksag Date: 2018-06-12.18:30:57
The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance.

Closing this issue.
Date User Action Args
2018-06-12 18:30:57berker.peksagsetstatus: chatting -> resolved
nosy: + berker.peksag
messages: + msg3491
2012-03-19 12:29:27tshepangsetnosy: + tshepang
2012-01-23 21:56:45Retrosetmessages: + msg2371
2012-01-23 21:09:31ezio.melottisetpriority: critical -> bug
nosy: + loewis, ezio.melotti
status: unread -> chatting
messages: + msg2370
title: ProgrammingError revealing server info -> ProgrammingError while deleting patch set
2012-01-23 20:23:06Retrocreate