Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master IgniteThinClientTest:
IgniteClientTestSuite: IgniteClientReconnect
Hi Igniters! The deadline for Ignite Summit Europe abstract submission has
been extended! We are now accepting abstracts through September 27, 2022.
If you consider participating in this year's event, now is the time! If you
have already started your submission process but have not yet finished
Thanks for the explanation.
Yes, I think we can apply the same color scheme everywhere, but let's hear
more opinions.
On Tue, Sep 6, 2022 at 1:10 PM Pavel Pereslegin wrote:
> Hello Pavel,
>
> I decided that it's safer to apply this only to our tests first, and
> then if everything is ok, apply
Hello Pavel,
I decided that it's safer to apply this only to our tests first, and
then if everything is ok, apply the same logger pattern to the default
production log4j-config,
If you think it's worth applying them now to the production config - I
can do it.
вт, 6 сент. 2022 г. в 12:33, Pavel
Looks great!
However, I'm a bit confused - does it apply to node output in production
build?
Why does it say "test console output"?
On Tue, Sep 6, 2022 at 12:20 PM Mirza Aliev wrote:
> Hello Pavel! Looks awesome! Thank you for the enhancement!
>
> вт, 6 сент. 2022 г. в 10:37, Pavel Pereslegin
Hello Pavel! Looks awesome! Thank you for the enhancement!
вт, 6 сент. 2022 г. в 10:37, Pavel Pereslegin :
> Hello Igniters!
>
> Recently completed Ignite migration to use log4j2 [1].
> Log4j2 supports ANSI colorization in the console [2], which can help
> in parsing log output.
> As an
Hello Igniters!
Recently completed Ignite migration to use log4j2 [1].
Log4j2 supports ANSI colorization in the console [2], which can help
in parsing log output.
As an experiment, I would like to colorize the test console output [3].
The color palette is similar to spring boot, see light [4]
