Qwen3.8-Max insights: https://chat.qwen.ai/s/87951950-46a3-4e64-a2af-60f51458a089?fev=0.2.82

Models used:

• GPT 5.5 (Codex, from JetBrains PyCharm) for the schema generation and the tests
• Qwen 3.8 for code review

I wonder if T1681 couldn't host them too. If so:

Patch written to test Codex. Model: GPT-5.5 (High).

Remove unused uids

Improve comment

Actually rewrite the file too

Avoid too many blank lines in Markdown rendering

Improve description

No please revert back to the version with innodb_buffer_pool_size = {{ innodb_buffer_pool_size }}.

That will be useful to implement a bunch of values for T2337

I confirm we probably don't need it on WindRiver right now.

Tested, works fine.

Computed on db-B-001, got 1 Gb using POWER(1024,3) but only 139 Mb using POWER(1024,2), so we're good with the default value there for now.

I see 3 blocks with the same 302 redirect.

Instead of documenting the error in a warning block, I'd suggest we keep a primary callout block with directly the good instructions you wrote.

Works like a charm.

To help edit vhosts, I've used the following sed expressions:

We can live with that, as there is work in progress to:

• at Nasqueron, migrate certificates to acme.sh
• on FreeBSD ports, prepare Salt for Python 3.12

It could be solved upstream with 3006.26.

@yousra It seems better with last Salt versions on 3006 LTS branch.