Trace flag doesn't work with --strip-linebreaks

[jwitz]

What happened?

After upgrading from 9.12 to 11.3, using --trace true gives the same output as without using the flag.

What did you expect to happen?

The command should output debugging and trace logs, currently it is showing neither.

How can we reproduce the behavior you experienced?

Run the same command with and without --trace true. The output is the same.

This was identified when trying to debug a 400 error from Confluence.

Further Information (please complete the following information)

• Mark Version (mark --version): 11.1
• Mark Parameters: --trace true
• Environment specific Information: [e.g. running in Github Actions, or on Mac OS X, etc.]: Jenkins pipeline on Linux

[mrueg]

Thanks for the report! Could you test with the versions released between v9.3 and v11.3, at which version the trace command stops failing for you?

[jwitz]

@mrueg My apologies, this is not an upgrade bug but rather a bug that occurs when --strip-linebreaks is specified with --trace. On 11.3, confirmed trace logs work but stop showing if also configured with --strip-linebreaks

[mrueg]

for my understanding: and this bug is not on 9.12? Could you maybe test v10 and v11? That would help me limit the changes that could cause it.

[jwitz]

@mrueg I just checked: This bug is present in both v11 and v9, since 9.10.0 when the strip-linebreaks flag was first introduced.

[mantzas]

@jwitz After merging the #542 the trace flag does not exist anymore. Would you like to reevaluate if the problem still insists?