Why are console log strings trimmed?

Docker Desktop
1

After last update of DockerDesktop for MacOs (v.4.40.0) every lines in log are trimmed and it leads to unreadable debug logs!
Just as examples:
This is how I see the swagger print from Fastify printRoutes() method

[INFO]: └── (empty root node)
├── /
│ └── api/v1/exports/
│ └── :customerId|:orderId
│ └── /
│ ├── batches (POST)
│ └── send-order-confirmed-pdf (POST)
└── * (OPTIONS)

And this is an example of a JSON.stringify(myObj, null, 2)

Query: {
where: { name: { and: [Array] } },
order: [ 'name', 'ASC' ],
include: [
{
as: 'customers',
attributes: [],
model: Customer,
required: true,
through: [Object],
where: [Object]
},
{
as: 'custom_batches',
model: CustomBatch,
required: false,
where: [Object]
}
]
}

This is a very short json but think about a veri large one with a lot of nestings!
So, why you chose for this (in my opinion ridicolous) choice?

Best regards,
Mirko

2

You are on a Docker Community forum where most of us just community members, but I could reproduce the issue and see that while the logs are shown correctly from the command line, Docker Desktop removes the leading spaces.

I didn’t notice, because I always use the terminal, but if you want the developers to know about the bug, you can report it on GitHub

I don’t think it was intentional.

4

Tank you for reply, surely I’ll post on GitHub.
I also hope that it was not intensional because debug in that way is nearly impossible!
Regards

5

It wasn’t necessary to post the issue on GitHub because the issue has been fixed in the new version (4.41.0).

6

Probably the fixed issue.

7

That was probably another, similar issue happening in the command line. I had newer versions than mentioned in the GitHub issue and logs were broken only on the GUI.

I actually shared this new issue in an internal channel one day before 4.41 was released, but it was most likely already fixed by then.