[07:54] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths edited [pull request #2521](https://github.com/MirServer/mir/pull/2521): Allow clients to get repeated string options
[08:47] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from wmww for [pull request #2522](https://github.com/MirServer/mir/pull/2522): spread: output test failures
[08:47] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [pull request #2522](https://github.com/MirServer/mir/pull/2522): spread: output test failures
[08:47] <Saviq> > Is it possible to add `CTEST_OUTPUT_ON_FAILURE=1` or something like that to CI so I can see the output when cmake tests fail?
[08:47] <Saviq> Of course :point_up:
[08:48] <Saviq> FWIW, you can't link to the raw logs, as that link expires, you need to link to the web results
[09:00] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [pull request #2521](https://github.com/MirServer/mir/pull/2521): Allow clients to get repeated string options
[09:40] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2516](https://github.com/MirServer/mir/pull/2516): Bump MirAL so to version 5 and MirAL version to 3.6
[09:57] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2523](https://github.com/MirServer/mir/pull/2523): Allow servers to get repeated string options
[09:57] -GitHub[m]:#mir-server-  
[09:57] -GitHub[m]:#mir-server- > This capability exists in the mirserver API (as used by `driver-quirks`) but was never exposed through MirAL
[11:19] <alan_g[m]> Saviq, Sophie has a bunch of PRs up that need rework (because of Sophie's other PRs that landed). If you've headspace, you could lighten the load by reviewing #2523
[11:47] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths edited [pull request #79](https://github.com/MirServer/ubuntu-frame/pull/79): Don't try to use evdi
[11:50] <Saviq> alan_g will do
[13:58] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2524](https://github.com/MirServer/mir/pull/2524): Fix regenerate-miral-symbols-map.py
[13:58] -GitHub[m]:#mir-server-  
[13:58] -GitHub[m]:#mir-server- > ...so it regenerates symbols.map correctly. (We accidentally broke it in #2516)
[14:10] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2523](https://github.com/MirServer/mir/pull/2523): Allow servers to get repeated string options
[14:37] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] edited [pull request #79](https://github.com/MirServer/ubuntu-frame/pull/79): [Merged by Bors] - Don't try to use evdi
[14:37] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] closed [issue #14](https://github.com/MirServer/ubuntu-frame/issues/14): ubuntu-frame may fail to start on hybrid PCs
[14:37] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] closed [pull request #79](https://github.com/MirServer/ubuntu-frame/pull/79): [Merged by Bors] - Don't try to use evdi
[16:00] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2525](https://github.com/MirServer/mir/pull/2525): Fix CommandLine strings option
[16:23] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2522](https://github.com/MirServer/mir/pull/2522): spread: output test failures
[18:06] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2524](https://github.com/MirServer/mir/pull/2524): Fix regenerate-miral-symbols-map.py
[18:06] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2525](https://github.com/MirServer/mir/pull/2525): Fix CommandLine strings option
[20:33] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [pull request #2526](https://github.com/MirServer/mir/pull/2526): Add surface_ready() shell/wm method
[20:33] -GitHub[m]:#mir-server-  
[20:33] -GitHub[m]:#mir-server- > Alternative to #2506. Makes the surface ready notification come from the frontend instead of being based on when a surface gets it's first buffer (in practice it should be the same behavior, but this architecture gives us more flexibility to control in the frontend when a surface is ready). Most importantly, no messy observer logic.