Debug log gets truncated

82 views
Skip to first unread message

eazim...@aquivalabs.com

unread,
Aug 30, 2017, 9:08:20 AM8/30/17
to Illuminated Cloud General Discussion
Hello Scott!

I've encountered the same issue described here https://groups.google.com/a/illuminatedcloud.com/forum/#!topic/discussion/8AJufBpBjUA . The thing is, it happened to me with debug log size <2 MB.
The reason why I receive "Invalid Apex log header" is, because for some reason, illuminated loads not whole log, but only last part of it without headers.
Debug log in salesforce "Debug Logs" looks something like:

20.0 APEX_CODE,DEBUG;APEX_PROFILING,INFO;CALLOUT,INFO;DB,INFO;SYSTEM,DEBUG;VALIDATION,INFO;VISUALFORCE,INFO;WAVE,INFO;WORKFLOW,INFO
05:50:54.0 (414507)|USER_INFO|[EXTERNAL]|005123123123123123|bestUserEver|Pacific Standard Time|GMT-07:00
EXECUTION_STARTED
....about 2 MBs of debug....
EXECUTION_FINISHED


while in Intellij it looks like:
CONSTRUCTOR_ENTRY|[182]|<init>() //it loads not the whole debug log, but starts from a random part of it.
...some other execution debug...
05:50:54.505 (4531592359)|WF_ACTIONS_END| //and ends in a random part.

Is it a known issue? Is it possible to do something with it?

Thank you in advance!

Evgeny.

sc...@illuminatedcloud.com

unread,
Aug 30, 2017, 9:17:17 AM8/30/17
to Illuminated Cloud General Discussion
Evgeny, it's a known issue in that I've heard of it happening, but I haven't been able to reproduce and therefore troubleshoot it.  If you have it in this state and wouldn't mind helping with some troubleshooting, that will hopefully help get to the bottom of what's going on.  Feel free to contact me at sup...@illuminatedcloud.com if you're able to do so and we can talk about how to corner and hopefully resolve this issue.

Regards,
Scott

sc...@illuminatedcloud.com

unread,
Aug 30, 2017, 11:00:40 PM8/30/17
to discu...@illuminatedcloud.com
Evgeny was able to create a reproducible test case that helped me figure this out. Thanks, Evgeny!  Basically IntelliJ has a setting for the console components into which the logs are written, and it maxes out at 1MB by default.  Of course, logs max out at 2MB, hence the truncation.

I've just submitted a change that auto-adjusts this upward for you, but if you're running into this issue between now and when I release that update, here's where you can set it yourself:


Anyway, I'll be glad to have this one fixed as it's always annoyed me that I couldn't reproduce it easily myself. Thanks again to Evgeny for the help getting to that point (and I'm actually quite embarrassed at how simple it was to reproduce)!

Regards,
Scott
Reply all
Reply to author
Forward
0 new messages