Simplify settings properties definitions #1501
equeimmain.yml
on: pull_request
build-flatpak
7m 22s
build-windows-mingw
4m 8s
reuse-lint
24s
Matrix: build-deb
Matrix: build-macos / build-macos
Matrix: build-rpm
Matrix: build-windows-msvc
Annotations
13 errors and 70 warnings
|
build-windows-mingw:
src/ui/screens/settingsdialog.cpp#L72
no member named 'darkThemeMode' in 'tremotesf::Settings'; did you mean 'get_darkThemeMode'?
|
|
build-windows-mingw:
src/ui/screens/settingsdialog.cpp#L75
no member named 'useSystemAccentColor' in 'tremotesf::Settings'; did you mean 'get_useSystemAccentColor'?
|
|
build-windows-mingw:
src/ui/screens/settingsdialog.cpp#L80
no member named 'setDarkThemeMode' in 'tremotesf::Settings'; did you mean 'set_darkThemeMode'?
|
|
build-windows-mingw:
src/ui/screens/settingsdialog.cpp#L83
no member named 'setUseSystemAccentColor' in 'tremotesf::Settings'; did you mean 'set_useSystemAccentColor'?
|
|
build-windows-mingw
Process completed with exit code 1.
|
|
build-windows-msvc (msvc) / build-windows-msvc (amd64_arm64, arm64)
The run was canceled by @equeim.
|
|
build-windows-msvc (msvc) / build-windows-msvc (amd64_arm64, arm64)
The operation was canceled.
|
|
build-windows-msvc (msvc-clang) / build-windows-msvc (amd64, x86_64)
The run was canceled by @equeim.
|
|
build-windows-msvc (msvc-clang) / build-windows-msvc (amd64, x86_64)
The operation was canceled.
|
|
build-windows-msvc (msvc) / build-windows-msvc (amd64, x86_64)
The run was canceled by @equeim.
|
|
build-windows-msvc (msvc) / build-windows-msvc (amd64, x86_64)
The operation was canceled.
|
|
build-windows-msvc (msvc-clang) / build-windows-msvc (amd64_arm64, arm64)
The run was canceled by @equeim.
|
|
build-windows-msvc (msvc-clang) / build-windows-msvc (amd64_arm64, arm64)
The operation was canceled.
|
|
reuse-lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-deb (debian:12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (debian:12)
'*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager' may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (ubuntu:24.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.10)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-rpm (fedora:41, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:41, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-deb (ubuntu:24.04)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-deb (ubuntu:24.04)
'memmove' forming offset 4 is out of the bounds [0, 4] [-Warray-bounds=]
|
|
build-rpm (fedora:40, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(struct function &)&__tmp + 16]._M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, gcc)
‘MEM[(const struct _Function_base *)&__tmp + 16B]._M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (fedora:40, clang)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(std::function<bool(char)>*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::function<bool(char)>::_M_invoker’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-rpm (opensuse/tumbleweed:latest, gcc)
‘*(const std::_Function_base*)((char*)&__tmp + offsetof(std::__detail::_StateT, std::__detail::_State<char>::<unnamed>.std::__detail::_State_base::<unnamed>)).std::_Function_base::_M_manager’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
build-flatpak
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-rpm (fedora:41, clang)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
macos-arm64-build-logs
Expired
|
42.1 KB |
|
|
macos-arm64-packages
Expired
|
30.9 MB |
|
|
macos-x86_64-build-logs
Expired
|
48.4 KB |
|
|
macos-x86_64-packages
Expired
|
31 MB |
|
|
windows-arm64-msvc-build-logs
Expired
|
265 KB |
|
|
windows-arm64-msvc-clang-build-logs
Expired
|
258 KB |
|
|
windows-x86_64-msvc-build-logs
Expired
|
438 KB |
|
|
windows-x86_64-msvc-clang-build-logs
Expired
|
309 KB |
|