>> we started seeing Surefire JVM fork crashes on various Windows 10
workstations when Jansi was active
Can you show me the log how it crashed, and maybe the dump file from
target/surefire-reports?
On Sun, Jun 28, 2020 at 7:29 PM Falko Modler wrote:
> Hi everyone!
>
> I recently ran into
Windows shell can't handle ANSI escape code: that's the purpose of Jansi, and
what is represented in JAnsi front page http://fusesource.github.io/jansi/
What makes you say that a Windows shell can handle the sequences?
Windows itself should be able to do this with this registry hack but I
have
Le lundi 29 juin 2020, 23:11:09 CEST Falko Modler a écrit :
> > on crashes, I don't have any clue: details welcome
>
> I see what I can do but please don't expect anything.
>
> > see https://github.com/fusesource/jansi/pull/150
> >
> > If we have multiple people using Windows to help test and
on crashes, I don't have any clue: details welcome
I see what I can do but please don't expect anything.
see https://github.com/fusesource/jansi/pull/150
If we have multiple people using Windows to help test and improve this, we
could probably finally merge the update
I'll try to support.
on crashes, I don't have any clue: details welcome
but on the performance impact of Jansi on Windows (to detect ANSI codes) when
there is much content (like with Surefire output), there is some partial work
started to improve by removing flush:
see https://github.com/fusesource/jansi/pull/150
Hi everyone!
I recently ran into problems when trying to get colored log output from
Quarkus tests (via Surefire): https://github.com/fusesource/jansi/issues/171
Coincidentally, we started seeing Surefire JVM fork crashes on various
Windows 10 workstations when Jansi was active (sorry, I do not
