Mateusz Slaski

Hello, I have the same issue. Is anyone working on it?

Hello @baev I'm also facing this issue with Cucumber6: allure-cucumber6-jvm

Hello @baev Do you have any plan to fix this issue?

@gnazgit @dineshmcac @baev I found a workaround for this issue related to @flaky annotation and I will prepare small script to fix report (don't have time to find a root...

From my point of view those incoming messages which failed check or exceed timeout should be treat as a "failed" ones. According to docs during matching all non-matching messages will...

Outbound message should be good enough. Ofc better to log all non-matching messages but in this case I see more difficult scenario. When im expecting some message using matching API...

> Summing up: > > * outbound messages: > > * log in TRACE at send time > * retain in memory for later logging if DEBUG is enabled and...

> @MSlaski For your purpose you have to define a logger in this way: > > ``` > > ``` > > Thus, you will receive only failure message logs,...

> > Unfortunately its not working like that > > @MSlaski Could you please clarify what specifically is not working? Are you still receiving logs for requests that did not...

@jlipps ``` ╭─[email protected] ~ ╰─➤ appium server --address 127.0.0.1 --port 4723 --allow-cors [Appium] Welcome to Appium v2.0.0-beta.66 [Appium] Non-default server args: [Appium] { [Appium] address: '127.0.0.1', [Appium] allowCors: true [Appium]...