Debug info was lost
andypost - July 4, 2009 - 17:06
| Project: | Project Issue File Review |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed |
Description
Everytime when exception happens on run.review watchdog receives ONLY internal $code but whole message (reason) is lost.
Same with rpc call - on debug stage we should have ability to view rpc.response data passed.
This could be very helpful when debuging both client and server side
| Attachment | Size |
|---|---|
| pifr2_debug.patch | 1.54 KB |
#1
XML-RPC result should posted after watchdog
#2
Changed to straight up watchdog() calls.
#3
This was committed, forgot to update status.
#4
@boombatower Logging all XML-RPC into watchdog is expensive so better leave this for
pifr_debug()!So when debug is disabled (production) watchdog stays clean.
#5
Another opinion - responce could be big and make bot slower
#6
Question to make sure then since PIFR_DEBUG still makes it run a single test...is this what you want?
#7
Final patch.
#8
Committed.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.