2.4.3.4 release notes

2.4.3.4

NOTE: I'm having a relatively minor shoulder repair surgery early next week that will significantly restrict my activities for a short period of time. As a result, there won't be a standard weekly update of IC for (hopefully just) 1-2 weeks. Aside from perhaps a day or two of actual outage immediately following the surgery, I do plan to provide both sales and (critical) technical support during this time, then return to the standard weekly update cadence. Apologies in advance for any inconvenience that this might cause.

• Issue 3043 - Hopefully put to rest the "Too few bytes returned by the publisher" error by enabling the Enable workaround for HTTP 411 issue connection option by default. If you continue to see this issue — or any new issues introduced by this change — please let me know so that I can address them ASAP.
• Added limited support for read-only expression evaluation in the Apex Offline Debugger. Ad hoc expression evaluation is not supported, but it does properly evaluate very simple name reference expressions that resolve to stack, member, and class variables, the last by class-qualified name or, when in the context of the containing class, unqualified name. This improvement was less about being able to evaluate user-entered expressions and more about showing variable values on mouse-over, but a side-effect of the change is that you can now add watch variables by name and observe their values while debugging.
• Fixed an issue in the Apex Offline Debugger where METHOD_ENTRY would be called with a duplicate constructor name for Flow.Interview.* constructors resulting in unbalanced stack frames.
• Improved error reporting in SOQL Query tool window tabs when the Use Tooling API option and the selected SObject type don't match properly.