Malithi,
Can we fix this? If not errors from Jaggery are not readable.
On Fri, Dec 18, 2015 at 2:37 PM, Sajith Ariyarathna
wrote:
> Hi Sumedha,
>
> This happens due to a security fix done for Carbon 4.4.2. Please refer Dev
> mail thread [1].
>
>
> [1] [Dev] Issue in carbon
Hi Sumedha,
This happens due to a security fix done for Carbon 4.4.2. Please refer Dev
mail thread [1].
[1] [Dev] Issue in carbon logs after changing carbon.kernel.version from
4.4.1 to 4.4.2
Thanks.
On Fri, Dec 18, 2015 at 1:12 PM, Sumedha Rubasinghe
wrote:
> Sajith,
>
Hi Sumedha,
We are sanitizing only the logging message. In Jaggery, stack traces are
sanitized since log.error(e); is used rather than log.error(message, e);.
This is also discussed at [1]. I think this should be fixed from jaggery
code.
[1] [Dev] Issue in carbon logs after changing
Sajith,
What is the reason for following exception to be printed in an unformatted
manner?
>
[2015-12-18 13:01:35,127] ERROR {JAGGERY.config.app:js} -
org.mozilla.javascript.WrappedException: Wrapped
java.lang.ArrayIndexOutOfBoundsException: 1
(/publisher/modules/data/driver.js#40)_ at