Rudder

Its bugfix will be in the next version

Jean, can you please elaborate on this problem?

This bug report is incomplete, and is not understandable by anyone other than you without more details... Can you add in a description of the problem, copies of error messages, a screenshot of it failing, or something similar, to help other developers understand what is happening here?

Thanks!

On the screenshot, we can see that after a click on the #1333 event log, unstead of showing more information on the event, it just draw a second line under the current line (that's why the line seems bold, in fact there are 2 lines).

2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.

With be250e549d68ea38725603d84c44b42a7a3fc14f. We have the following result:

Is the xml data is really relevant for that kind of event? (We don't always have data for this event)

Jean VILVER wrote:

With be250e549d68ea38725603d84c44b42a7a3fc14f. We have the following result:

Is the xml data is really relevant for that kind of event? (We don't always have data for this event)

No, it isn't really for now, but it may become so in the future (for example with information about what change caused this automatic deploy). For now it's good to leave it.

Should we display a message explaining the xml data?

Jean VILVER wrote:

Should we display a message explaining the xml data?

Not for now, since as you pointed out there's nothing really in there to explain...

Jonathan CLARKE wrote:

Jean VILVER wrote:

Should we display a message explaining the xml data?

Not for now, since as you pointed out there's nothing really in there to explain...

All right. I'm changing this ticket to Technical Review.

This looks valid, thank you Jean