Comments for TehNrd

Comment on If Computers Could Barf – Salesforce Debug Log by John Hart

John Hart — Tue, 09 Mar 2010 19:12:57 +0000

The big issue for me is that I can’t get the output of System.debug() statements without also getting METHOD_ENTRY/EXIT spew (as both are in the “Apex Code:DEBUG” level).

I think System.debug() statements should be placed into a separate Log Level than METHOD_ENTRY/EXIT. Perhaps METHOD_ENTRY/EXIT should be moved into the “Fine” log level.

Note the Log Level-vs-Events issue is confused, because there isn’t an Event for System.debug() statements – they show up at DEBUG, but the System Log’s “Events” list only adds METHOD_ENTRY/EXIT when you go from “INFO” to “DEBUG”.

Also, it would be useful to break METHOD_ENTRY/EXIT into USER_METHOD_ENTRY/EXIT and SYSTEM_METHOD_ENTRY/EXIT. The first only traces non-System methods; the second traces system methods. They should be placed in “FINE” and “FINER” levels, respectively.

Comment on If Computers Could Barf – Salesforce Debug Log by Gary B

Gary B — Tue, 09 Mar 2010 13:01:26 +0000

@Gary B OK, I take part of that back - it seems (some) method names *are* in the log, apologies!

Comment on If Computers Could Barf – Salesforce Debug Log by Gary B

Gary B — Tue, 09 Mar 2010 12:46:39 +0000

@Rich Unger
Rich, I can understand this is laying the foundations for things to come, and I get an idea of what’s coming down the line… but in the here and now, things appear to have gotten more difficult.

I’m persevering as I don’t want to write it off just because it’s different; similarly, I’m wary of making myself look an idiot because I’ve yet to grok how the feature actually works. But as far as I can tell, names of custom built methods no longer appear in the log output, which is a massive thorn in my side. I’m trying to investigate something in a production environment, updating code and deploying just for the sake of some debug statements is not exactly ideal for me…

And as for the “makes parsing easier” – are there any tools out there at the moment that can help with this with output from Spring 10?

Apologies for shooting the messenger, and I realise I’m partly to blame as I didn’t try it earlier and offer my feedback!

Comment on Super Cool Advanced Lookup Component by Shan

Shan — Mon, 08 Mar 2010 19:05:19 +0000

One more thing… When I select another Value… and hit Show, the value is not being picked up…
I am basically using your component in a dynamic SOQL reporting design…
Is there a way to refresh the value or something…

Comment on Super Cool Advanced Lookup Component by Shan

Shan — Mon, 08 Mar 2010 18:05:31 +0000

Hi:
Love this compenent… How would this work if you have a child object. Basically I have an object Course which has a lookup to Contact. I want to put a field out there which goes off the contact field in Course object??
Otherwise awesome…

Comment on If Computers Could Barf – Salesforce Debug Log by Mike Eaton

Mike Eaton — Fri, 05 Mar 2010 18:27:41 +0000

Agree with you 100%. I feel like we’ve taken a giant step backwards. Hopefully we’ve hit the bottom of the barrel and can only go up from here. Keep up the good work!

Comment on If Computers Could Barf – Salesforce Debug Log by Rich Unger

Rich Unger — Thu, 04 Mar 2010 00:27:38 +0000

BTW, one workaround you can use if you just want to see the System.debug() output is to use the logging levels, e.g.: System.debug(LoggingLevel.INFO, ‘foo’)
and set your filter for the APEX_CODE category to INFO. The METHOD events get logged in the DEBUG level, which is one below INFO.

Comment on If Computers Could Barf – Salesforce Debug Log by Jason

Jason — Mon, 01 Mar 2010 23:20:29 +0000

@Rich

Being easy to parse is nice…. but since I am human, not a computer, I would say being easy to read takes priority for me.

I’m guessing (hoping) now that it’s easy to parse you will have some UI improvements that will make it easy to read.

I’m glad to hear you can see, in it’s current state, it is rough to use and improvements are on the way.

Comment on If Computers Could Barf – Salesforce Debug Log by Rich Unger

Rich Unger — Mon, 01 Mar 2010 23:04:33 +0000

The point of the new logging format is to make it more easily parseable. The METHOD_ENTRY lines allow such a parser to trace where it is in the call stack.

What you see in this release is the first step on a longer road towards making the development experience with apex more enjoyable. There was a lot that had to be done on the back end before we could really do what we wanted with the interface.

Believe me, I know how rough this feature feels right now. Please stay tuned!

Comment on If Computers Could Barf – Salesforce Debug Log by Manu

Manu — Mon, 01 Mar 2010 21:35:58 +0000

What great timing for the post – I had the (mis)fortune of trying to debug code while deploying from a Win’10 Sandbox to a Spring’10 production org today that had a multitude of custom apps already on! The horror of the new logger struck me when it didn’t point out which row of which function of which class was failing! if it wouldn’t have been my own code, I’m not sure how much time it’d take to debug and fix it! Luckily, that wasn’t so but it sure’s going to take some time getting used to the new logging for sure!

As usual, great post, Jason!