Awesome thanks. Everything is working now.
I've used the scheduler monitor a decent amount and it has worked pretty
well for me. This is the first bug I've noticed but if I find more I'll be
sure to let you know. The only tweak I've made is the output from my tasks
contains lots of debug information when things go wrong and it was hard to
interpret since newline characters were not being displayed in the table.
I simply edited line 29 in run_details.html:
<td>{{=XML(r_.run_output.replace('\n', '<br />'))}}</td>
It's not the prettiest thing in the world. If there are lots of newline
characters it makes the output look almost doubled spaced, but it is useful
and does the trick.
Thanks!
On Saturday, October 19, 2013 8:57:14 AM UTC-4, Niphlod wrote:
>
> BTW, found the issue with comfort scheduler. Will update as soon as github
> comes back.
>
> [edit] Done
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
