Stack trace of errors to console when running bots-engine.py?

32 views
Skip to first unread message

clemper

unread,
May 23, 2012, 11:53:34 AM5/23/12
to bots...@googlegroups.com
Hi,

Is it possible to get the stack trace of any errors printed directly to the console when running bots-engine.py ?  I have tried setting all possible debug flags to True in bots.ini and settings.py, but I just get a summary indicating that an error has occurred.  I then have to go to the web interface and browse to the error to see what went wrong.   

Thanks,
Chris Lemper

henk-jan ebbers

unread,
May 23, 2012, 12:04:53 PM5/23/12
to bots...@googlegroups.com

1. yes, bots-engine only indicates the results (handy if results are OK/as expected)
2. look in bots interface. For most errors, this is the most easy way.
3. look in bots/botssys/logging/engine.log; this is useful for more elaborate logging. As a lot is logged, this is not always handy.

also in the wiki:
http://code.google.com/p/bots/wiki/Debug


henk-jan

clemper

unread,
May 23, 2012, 12:29:27 PM5/23/12
to bots...@googlegroups.com
Thanks for the reply.  It verifies my understanding.  It would be very useful to have an option to log errors directly to the console during development.  I am new to Python and Bots and unfortunately make a lot of mistakes.  It would greatly speed it up to not have to go to the UI, click, click, click, view to see the error.  I know it doesn't seem like a lot of effort but when you do it 20+ times in a row it adds up.  However, I do think tailing engine.log in a separate console is a reasonable solution.

Thanks,
Chris

henk-jan ebbers

unread,
May 23, 2012, 12:38:55 PM5/23/12
to bots...@googlegroups.com
go to menu:last run->incoming.
after another run press F5

it might be easier to run bots-engine from the commandline

hope that helps,

henk-jan

On 05/23/2012 06:29 PM, clemper wrote:
> Thanks for the reply. It verifies my understanding. It would be very useful to have an option to log errors directly to the console during development. I am new to Python and Bots and
> unfortunately make a lot of mistakes. It would greatly speed it up to not have to go to the UI, click, click, click, view to see the error. I know it doesn't seem like a lot of effort but when you
> do it 20+ times in a row it adds up. However, I do think tailing engine.log in a separate console is a reasonable solution.
>
> Thanks,
> Chris
>
> On Wednesday, May 23, 2012 10:04:53 AM UTC-6, eppye wrote:
>
>
> 1. yes, bots-engine only indicates the results (handy if results are OK/as expected)
> 2. look in bots interface. For most errors, this is the most easy way.
> 3. look in bots/botssys/logging/engine.log; this is useful for more elaborate logging. As a lot is logged, this is not always handy.
>
> also in the wiki:
> http://code.google.com/p/bots/wiki/Debug <http://code.google.com/p/bots/wiki/Debug>
Reply all
Reply to author
Forward
0 new messages