Re: Issue with pyramid 1.2a+

Thanks, I have tested it and it works for the issue I was having. This is going to make debugging much easier. File "...adviewer/ads/controller.py", line *38*, in save_rating member_urls_today[str(data['index'])] = data On Tue, Aug 30, 2011 at 3:47 PM, Chris McDonough wrote: > On Tue, 2011-0

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 15:34 -0500, Michael Merickel wrote: > The toolbar should be configured to *always* dump out the url to the > traceback in the logger as well as display the url in the web page > rendered for the traceback. > > > I think part of the point of the debugtoolbar is the interacti

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 15:34 -0500, Michael Merickel wrote: > The toolbar should be configured to *always* dump out the url to the > traceback in the logger as well as display the url in the web page > rendered for the traceback. It currently does the former (at least when "debugtoolbar.intercept_e

Re: Issue with pyramid 1.2a+

The toolbar should be configured to *always* dump out the url to the traceback in the logger as well as display the url in the web page rendered for the traceback. I think part of the point of the debugtoolbar is the interactive traceback so I'd like to see 'debug' remain as the default, or rename

Re: Issue with pyramid 1.2a+

I like that idea, then at least there is the option of having debugging controls for those who want/need them. On Tue, Aug 30, 2011 at 1:15 PM, Chris McDonough wrote: > On Tue, 2011-08-30 at 14:01 -0500, Michael Merickel wrote: > > The way weberror worked is that it'd dump the URL to the console

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 14:01 -0500, Michael Merickel wrote: > The way weberror worked is that it'd dump the URL to the console, and > you could visit that url to see the traceback. I think this was fairly > reasonable. So I have this working on a branch. It keeps exceptions around and dumps a URL

Re: Issue with pyramid 1.2a+

"Or possibly folks that want this URL on the OS console are just going to need to live without interactive debugging; they might only have the ability to view the traceback in history instead of having a full-on debugger at the URL." I think that idea is a good solution. It is better to be able to

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 14:32 -0500, Michael Merickel wrote: > I don't see this as an issue because if you're deploying with the > debugtoolbar enabled you should be shot. Regardless adding the token > to the url doesn't sound like a big deal. I guess we'll just have to > think about it. It doesn't

Re: Issue with pyramid 1.2a+

I don't see this as an issue because if you're deploying with the debugtoolbar enabled you should be shot. Regardless adding the token to the url doesn't sound like a big deal. I guess we'll just have to think about it. -- Michael -- You received this message because you are subscribed to the

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 14:01 -0500, Michael Merickel wrote: > The way weberror worked is that it'd dump the URL to the console, and > you could visit that url to see the traceback. I think this was fairly > reasonable. Allowing access via a URL to a traceback display was a security risk if the URL

Re: Issue with pyramid 1.2a+

The way weberror worked is that it'd dump the URL to the console, and you could visit that url to see the traceback. I think this was fairly reasonable. -- Michael -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 11:23 -0700, Bruce Wade wrote: > Please see the attached screen shots. There is no useful information > in the console to help debug this example issue. I believe older > versions of pyramid would have displayed more information. Unless we > are missing a configuration to disp

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 10:46 -0700, Bruce Wade wrote: > Trace back works great until there is a 500 error, like trying to > using a Unicode number to an index for a list. If the renderer wasn't > set to json the error would be displayed however when the renderer is > json there is no message to trac

Re: Issue with pyramid 1.2a+

Trace back works great until there is a 500 error, like trying to using a Unicode number to an index for a list. If the renderer wasn't set to json the error would be displayed however when the renderer is json there is no message to trace, and the js console only says 500 server error. On Tue, Au

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 10:25 -0700, Bruce Wade wrote: > OK Thanks, we like the debug tool bar so we will have to see how our > team can change things to make it easier debugging view errors when > using ajax. FWIW, personally, I just use the traceback output on the console. There's also a pyramid_e

Re: Issue with pyramid 1.2a+

OK Thanks, we like the debug tool bar so we will have to see how our team can change things to make it easier debugging view errors when using ajax. On Tue, Aug 30, 2011 at 10:19 AM, Chris McDonough wrote: > On Tue, 2011-08-30 at 10:18 -0700, Bruce Wade wrote: > > Thank you for your response at

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 10:18 -0700, Bruce Wade wrote: > Thank you for your response at least I know I am not loosing my > mind :D. > > > Is there any plans on getting ajax/json support into the debug > toolbar? No. - C > > > -- > Bruce > > On Tue, Aug 30, 2011 at 10:06 AM, Chris McDonough

Re: Issue with pyramid 1.2a+

Thank you for your response at least I know I am not loosing my mind :D. Is there any plans on getting ajax/json support into the debug toolbar? -- Bruce On Tue, Aug 30, 2011 at 10:06 AM, Chris McDonough wrote: > On Tue, 2011-08-30 at 09:55 -0700, Bruce Wade wrote: > > Hello, > > > > > > I not

Re: Issue with pyramid 1.2a+

On Tue, 2011-08-30 at 09:55 -0700, Bruce Wade wrote: > Hello, > > > I noticed a change in how paster is handling errors. Prior to v1.2a3 > when I used renderer='json' and I had a 500 server error the console > window would provide me with the debug URL to check out. However now > there is no URL

Issue with pyramid 1.2a+

Hello, I noticed a change in how paster is handling errors. Prior to v1.2a3 when I used renderer='json' and I had a 500 server error the console window would provide me with the debug URL to check out. However now there is no URL displayed wit