Skip to content

bug: master's app builds are red β€” #2909 turned on the frontend conversion group with 63 unconverted files leftΒ #2938

Closed

Description

@zackees

Summary

Master (as of 6c5fd4516) fails every app build lane: Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust),
Build 🧱 / Flatpak πŸ“¦, Build 🧱 / macOS 🍏 (arm64) and (x86_64). All of them stop in the
frontend C++ compile with -Werror=conversion / -Werror,-Wsign-conversion, in files that
#2909 did not convert.

Evidence

workflow_dispatch of scheduled.yaml on fix/2921-mp4-mux-conversions (that branch is rebased
onto 6c5fd4516; its own two files compile clean before this point), run
40902391979:

Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust)   job 123553698526  failure
Build 🧱 / Flatpak πŸ“¦                    failure
Build 🧱 / macOS 🍏 (arm64)              job 123553699030  failure
Build 🧱 / macOS 🍏 (x86_64)             failure

Ubuntu:

frontend/utility/ExtraBrowsersModel.cpp.hpp:20:34: error: conversion from 'qsizetype' {aka 'long long int'} to 'int' may change value [-Werror=conversion]
frontend/utility/ExtraBrowsersModel.cpp.hpp:33:31: error: ... same
frontend/utility/ExtraBrowsersModel.cpp.hpp:108:32: error: ... same
frontend/utility/ExtraBrowsersModel.cpp.hpp:190:37: error: ... same

macOS arm64:

[obs-studio] Compiling qt-wrappers.core+.hpp.cpp
##[error]implicit conversion changes signedness: 'int' to 'uint32_t' (aka 'unsigned int') [-Werror,-Wsign-conversion]
   43 |         return obsModifiers;

Root cause

18f8a3f22 (#2909, merged 2026-10-29 14:10 UTC) added
-Wconversion;-Wsign-conversion;-Wfloat-conversion to the obs-studio frontend target in
frontend/CMakeLists.txt:203 together with fixes for only the first group of files. Its own commit
message says so:

Partial: the 48 diagnostics in the frontend.* unity units ... The target-wide ratchet cannot
build until the other 746 diagnostics in 63 files are fixed too, so this commit is not pushed on
its own.

The second half of that sentence did not hold: the flags landed with the partial fix.

PR CI never compiles the frontend (its Ubuntu lane builds no app), so the merge queue saw a green
PR; the breakage only shows in the master-push/dispatch app lanes, which is why master went red
without a PR going red.

Options

  1. Restore the pins for this target until the rest is converted β€” re-add
    -Wno-conversion;-Wno-sign-conversion;-Wno-float-conversion to obs-studio in
    frontend/CMakeLists.txt, with a ci/test_ci_*.py style pin that fails when the flags return, and
    land the 63 files as their own PRs. Restores every release lane immediately; matches what frontend: state the conversions the app target now reports (#2625)Β #2909's
    message said the ordering should be.
  2. Finish the remaining frontend conversions in one PR (~746 diagnostics / 63 files, size L) and keep
    the lane dark meanwhile, which keeps master's release artifacts unbuildable and blocks every open
    PR that needs a macOS or Ubuntu app build for evidence (including build(obs-outputs): state the mp4-mux and rtmp-hevc conversions macOS clang reports (#2921)Β #2922 and build(obs-outputs): state the rtmp-hevc record conversions (#2928)Β #2929).

Recommendation: option 1 now, then re-land per unity-unit group.

Not the cause

Not #2925/#2926/#2922: those touch plugins/obs-outputs/** only, and the failing files here are
frontend/shared C++ that no PR in flight modifies.

Activity

  1. added
    bugSomething isn't working
    P0Red master or broken release: drop everything (8 h claims)
    size:LSeveral days
    on Oct 29, 2026
  2. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Claiming: #2938

    Plan: turn the frontend conversion group green in place, one unity group per commit, so Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust), Flatpak, and both macOS app lanes compile again. -Wconversion/-Wsign-conversion stay on for the target; the fix is stating the conversions at the call sites, not relaxing the flag.

    1. Reproduce locally on Linux by compiling the obs-studio frontend target with the same flags, and record the first RED slice (the unity file that fails).
    2. Fix the reported sites (frontend/utility/ExtraBrowsersModel.cpp.hpp, frontend/qt-wrappers.cpp.hpp) with explicit casts, byte/behaviour-preserving; verify with a local build of the same target.
    3. Walk the remaining unity groups in the same way until the frontend target compiles clean, one commit per group.
    4. Add or extend a test that pins the flag set, so a new group cannot be turned on with unconverted files left, then open a PR Fixes #2938 from a clean master and let PR CI decide.

    This is a P0 blocking every app lane, so it goes first; PR follows as soon as the first group is verified.

  3. self-assigned this
    on Oct 29, 2026
  4. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Status on #2938 β€” the cause is narrower than the issue says, and the fix splits in two.

    1. Ubuntu + Flatpak came from a duplicate opt-in block, not from an unfinished conversion.
    frontend/CMakeLists.txt already opted obs-studio into -Wsign-conversion alone
    ("-Wconversion and -Wfloat-conversion keep the global pins for now"). #2909 appended a
    second
    target_compile_options(obs-studio ...) block at the end of the file naming all three
    groups, and its own commit message said 746 diagnostics in 63 files were still unconverted. The
    app configure compiles with CMAKE_COMPILE_WARNING_AS_ERROR=ON, so the lanes stopped on the first
    unconverted file. Removing that second block is the P0 fix and lands as #2944, with
    ci/test_frontend_conversion_optins.py holding the target to one opt-in block that names only the
    group it has converted.

    That is option 1 in the issue, scoped to the two groups #2909 added by mistake: -Wsign-conversion
    stays on for the target, the other two stay on the global pins until their files are clean.

    2. macOS is a different, older red. The 05:49 UTC scheduled.yaml on master (before #2909)
    already had Build 🧱 / macOS 🍏 (arm64) and (x86_64) failing while Ubuntu and Flatpak were
    green; the qt-wrappers.host-macos+.hpp.cpp return obsModifiers site is the sign-conversion
    error that run reports, and it is what #2940 states at the call site.

    Why PR CI was green on #2909. Build 🧱 / Qt Frontend Linux 🐧 is selected for frontend/
    changes and passed, but the app configure compiles a larger unity set than that lane, so
    frontend/utility/ExtraBrowsersModel.cpp.hpp was not in any unit it built. The lanes that break
    (Ubuntu 🐧 (OBS-Studio-Rust), Flatpak πŸ“¦, macOS) never run on a PR β€” a scheduled.yaml
    dispatch on the branch is still the only evidence for them.

    Next: #2944 for the pins (dispatch running on that branch for the Ubuntu/Flatpak lane evidence),
    #2940 for the macOS sign-conversion sites, then the remaining frontend groups convert file by file
    and the flag rejoins the single opt-in block in the PR that converts the last one. The claim stays.

  5. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Progress from the sanitizer dispatch on master (c2df54a7f, run 40919949570):

    • asan πŸ§ͺ is red for a frontend site, not for the C conversions. With mp4-mux.c.h and rtmp-hevc.c.h fixed on master, the lane's asan build got past them and stopped at:
    frontend/components/OBSAdvAudioCtrl.cpp.hpp:533:45: error: conversion to 'uint32_t' from 'int' may change the sign of the result [-Werror=sign-conversion]
    

    This is the 1 << mixerIdx / mixers & (1 << n) bath in OBSAdvAudioCtrl. #2952 fixes that whole file's site class (1u literals, no value change) and leaves the rest of the group to follow-ups.

    Nothing here needs a decision from you; the ratchet question in #2923's last comment does.

  6. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Progress (worker tick): the app-lane conversion fixes are landing β€” #2940 (conversion sites stated) and #2944 (global pins kept for the unconverted target) merged at 18:28 UTC, #2947 (qt-host macOS modifier return) is in the merge queue. The macOS lanes then reached the next files, which are tracked separately as #2950 (PR #2951: platform-osx.mm.hpp, properties-view.cpp.hpp, PluginModuleLoader_MacOS.mm.hpp). This issue stays open for the remaining unconverted app targets.

  7. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Status from the worker tick: the app-lane acceptance evidence is now being produced, on a tree that contains the fixes.

    Every app-lane run on master so far predates the fixes this issue tracks: the Release OBS-Studio-Rust failure at 15:58 UTC ran 3bff1d7c8 (15:33), i.e. before #2940 (17:17) and #2944 (18:28) landed, and the last full dispatch (40919949570) ran c2df54a7f. So its red Release gate 🚦 / Ubuntu + / Flatpak jobs β€” both stopping on frontend/utility/ExtraBrowsersModel.cpp.hpp:20,33,108,190 (qsizetype β†’ int) β€” are the same symptom this issue was filed for, not a new class.

    Dispatched scheduled.yaml on master 2fe262aa3: 40943427805. Its Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust), Build 🧱 / Flatpak πŸ“¦ and both macOS 🍏 build jobs are this issue's acceptance items; I will report the verdict and, if they are green, close this with the remaining-files list as the follow-up.

    In flight elsewhere, all linked here:

  8. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    First verdict from the master dispatch (40943427805, 2fe262aa3):

  9. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Verdict from the completed master dispatch (40943427805, 2fe262aa3).

    Green (the app lanes this issue opened):

    • Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) β€” success.
    • Build 🧱 / Windows πŸͺŸ (x64) and (arm64) β€” success.
    • Build 🧱 / Qt Frontend Linux 🐧, Build 🧱 / Flatpak πŸ“¦ β€” success.
    • Build 🧱 / Fast Gate ⚑, the Rust Tier 2 Linux matrix, Rust Tests πŸ¦€ and Rust Cross Lint πŸ¦€ (Windows, macOS) β€” success.

    So with #2940/#2944 on master the frontend conversion group's Linux and Windows app builds are clean. That half of the report is closed.

    Still red: Analyze πŸ”¬ / macOS 🍏 (clang-analyze), Build 🧱 / macOS 🍏 (x86_64), Build 🧱 / macOS 🍏 (arm64). Logs are published now, so here is what they actually say rather than the assumed class. The arm64 and x86_64 builds stop on eight -Wsign-conversion diagnostics in this tree, not in the Qt deps headers:

    File Lines
    frontend/utility/update-helpers.cpp.hpp 15, 16 (str.resize(size), vsnprintf(&str[0], size, ...))
    frontend/utility/WhatsNewInfoThread.cpp.hpp 33, 53, 57, 86, 176 (fileStream.write/read, tellg, gcount, VerifySignature)

    Those are exactly the sites PR #2951's fourth round states (e54bf8092), which is not on master yet. Its own macOS dispatch (40936503160) got past them and then stopped on six -Wsign-conversion errors whose locations are inside the .deps/obs-deps-qt6-2026-10-25-universal headers, the Decision needed: now open on #2950. So the macOS half of this issue is two layers deep and the second layer is a maintainer decision, not a source fix.

    Correction to this issue's own report: the 63 frontend sites it listed were real and are now stated; nothing in this run reproduces them on Linux or Windows.

    CEF Chromium Support 🌐 also failed in this run, by design (#1864), so it is not a health signal.

  10. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Verdict from the master dispatch, now that the run finished (40943427805, 2fe262aa3):

    So there is no new site here: master's macOS red is exactly the call-site list in #2951, which is a draft because its last dispatch round cleared every site in this tree and then stopped in the Qt 6.11 deps' own headers (qnamespace.h:1926,1930,1935, qversiontagging.h:80). That is the build-policy question now recorded as Decision needed: on #2950, which carries claim-blocked until a maintainer answers.

    State of this issue: Linux builds green; macOS waits on the #2950 decision, not on more conversion work here. Nothing needs a decision from you on this issue itself β€” I will post the next verdict after #2951's blocker is resolved and it is merged.

  11. zackees commented on Oct 29, 2026

    @zackees
    MemberAuthor

    Status (worker tick): the 19:48 UTC dispatch's result is in, and it is one commit stale.

    Run 40943427805 ran master 2fe262aa3 (19:48 UTC), i.e. before #2951 merged as 217b3cf08 (22:36 UTC):

    • Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) β€” success
    • Build 🧱 / Flatpak πŸ“¦ β€” success
    • Build 🧱 / macOS 🍏 (arm64) and (x86_64) β€” failure, but every diagnostic it reports is a site build: state the macOS conversion sites the mac lanes stop on (#2950)Β #2951 already states:
      • frontend/utility/WhatsNewInfoThread.cpp.hpp 33/53/57/86 (size_type↔streamsize, streamoffβ†’size_t, gcount())
      • frontend/utility/update-helpers.cpp.hpp 15/16 (int size β†’ std::string::resize/vsnprintf)
      • frontend/utility/WhatsNewInfoThread.cpp.hpp 176 (QByteArray::size() β†’ size_t)

    On 217b3cf08 all of those are static_casts in place (git show 217b3cf08 -- frontend/utility/WhatsNewInfoThread.cpp.hpp frontend/utility/update-helpers.cpp.hpp). So this run measures the pre-#2951 tree, not a new class.

    Dispatched scheduled.yaml on master 217b3cf08: 40970380763. The acceptance for this issue is that run's Ubuntu 🐧 (OBS-Studio-Rust) and Flatpak πŸ“¦ jobs (green above) plus the two macOS build jobs; I will report the verdict and close with the remaining-files list if macOS is green, otherwise split the next file class into its own ticket.

  12. 5 remaining items

  13. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Status (worker tick, obs-studio3): a scheduled.yaml dispatch on current master 43af74187 (the #2968 merge) β€” run 40978686832 β€” narrows this issue to one lane class that is not our source any more.

    Lane Result Where it stops
    Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) success β€”
    Build 🧱 / Flatpak πŸ“¦ success β€”
    Build 🧱 / Windows πŸͺŸ (x64) failure plugins/obs-qsv11/obs-qsv11.c.h(1072,25) C4310 / C2220 β€” the #2965 residual, fixed by #2969, which is queue position 1; (arm64) was cancelled behind it
    Build 🧱 / macOS 🍏 (arm64) failure .deps/obs-deps-qt6-2026-10-25-universal/lib/QtCore.framework/Headers/qnamespace.h:1926,1930,1935 and qversiontagging.h:80, all -Werror,-Wsign-conversion
    Build 🧱 / macOS 🍏 (x86_64) failure the same four deps-header sites
    CEF Chromium Support 🌐 failure by design while CEF 7871 lags Chrome (#1864)

    So the 63 unconverted frontend files and every first-party site in this report are now past the compiler: Linux and Flatpak app builds are green on master again, and Windows follows as soon as #2969 lands.

    What is left is the escalated build-policy question, not a conversion. Both macOS lanes stop only in the universal Qt 6.11 deps' own headers (qnamespace.h, qversiontagging.h) parsed into the frontend.signal-posix unity group. That is exactly the Decision needed: on #2950 (option 1: mark the .deps include directories SYSTEM for the app target; option 3: stop the macOS burndown and keep the pins), and it has no answer yet, so this lane stays red while those macOS app builds are unbuildable.

    Nothing else from this issue's list is red on the lanes above. I did not change a flag and did not open a policy PR: the choice between -isystem for deps includes and keeping the pins is the maintainer's, and it is recorded on #2950 with a one-word Decided: as the unblock.

    • Build 🧱 / Sanitize πŸ§ͺ was skipping on this dispatch (the scheduled default), so it carries no evidence either way.
  14. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Lane evidence from a scheduled.yaml dispatch on master 43af7418 (run 40978686832):

    Lane Result
    Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) success
    Build 🧱 / Flatpak πŸ“¦ success
    Build 🧱 / Windows πŸͺŸ (x64) failure β€” plugins/obs-qsv11/obs-qsv11.c.h(1072,25): error C2220 (C4310)
    Build 🧱 / macOS 🍏 (arm64) and (x86_64) failure β€” Qt 6.11 deps headers (qkeycombination.h / qnamespace.h:1926,1930,1935)
    Analyze πŸ”¬ / macOS 🍏 (clang-analyze) failure β€” same Qt deps headers

    So the frontend conversion scope this issue was opened for is done: Ubuntu and Flatpak are green with #2968's two scripts.cpp.hpp sites (174, 204) and nothing else in the frontend group reports.

    What is still red is not this issue's scope:

    Keeping this open until #2969 lands and the macOS decider answers, so the app-lane board is green end to end and not just for the frontend group.

  15. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Status (worker tick, obs-studio2): two things, one fix and one verdict.

    1. The last release-lane site in this issue's original log is now a PR. #2971 states the conversion at frontend/utility/ExtraBrowsersModel.cpp.hpp:190 (int i = deleted.size() - 1 β€” qsizetype to int), which is the one of the four diagnostics in Release OBS-Studio-Rust run 40906899118 that #2940 left behind. Its Build 🧱 / Qt Frontend Linux 🐧 lane is the direct GREEN evidence; asan is selected too, because the file is a compile input below the ratcheted frontend directory. Auto-merge is on.

    2. The red nightly Sanitizers run of 2026-10-29 13:40 (commit 32c4bcc1) is not a live failure. Every diagnostic in it is fixed by a commit merged after that run started:

    Lane Site in the 13:40 log Fixed by
    asan obs-ffmpeg-vaapi.c.h:434,435 (1 << log2_chroma) #2925 (6c5fd4516) β€” now 1u <<
    asan rtmp-av1.c.h:109,499,500, mp4-mux.c.h:524, rtmp-hevc.c.h:827,843 #2922 / #2925 β€” every site has its explicit cast on master
    valgrind v4l2-helpers.c.h:20 (PRIuFAST32 vs uint) #2925 β€” (uint_fast32_t) at both call sites

    I checked the current sources rather than trusting the run, and the lane was already re-run green on master after those merges: workflow_dispatch run 40962690971 on 9ffa4e65 finished success for asan πŸ§ͺ, valgrind πŸ§ͺ and tsan πŸ§ͺ (and 40942190769 on 6ca10e79 likewise). So the schedule should be green on its next pass; I canceled the redundant dispatch I had started before finding that.

    What is still red on the app lanes is only the .deps Qt 6.11 header question on #2950, unchanged by this tick.

  16. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Health update after #2968 and #2969 landed β€” the Linux/Flatpak half is now green on master, the Windows half was one regression from #2965 and is fixed.

    scheduled.yaml on master 43af74187 (40978686832, the commit before #2969):

    Nothing from the original report is left on any lane. Once #2950's decision is made and its PR lands, this issue can be closed; until then the only red is that decision.

  17. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Status on current master e2782b4ac (scheduled.yaml run 40983897736, worker tick obs-studio2):

    Release lane: #2971 (ExtraBrowsersModel.cpp.hpp:190, the one site from this issue's Release OBS-Studio-Rust log that #2940 left behind) is merge-queue position 1.

    So nothing in this issue's original list is red any more; once #2971 lands and #2950's include-directory decision is answered, this tracker has no children left and can close.

  18. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Lane evidence on current master e2782b4ac (worker tick, obs-studio4), and the one thing this run could not answer.

    scheduled.yaml dispatch run 40983897736 on e2782b4ac (the #2970 frontend-api ratchet):

    Job Result
    Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) success
    Build 🧱 / Flatpak πŸ“¦ success
    Build 🧱 / Windows πŸͺŸ (x64) success
    Build 🧱 / Windows πŸͺŸ (arm64) success
    Build 🧱 / Qt Frontend Linux 🐧 success
    Build 🧱 / macOS 🍏 (arm64) failure β€” Qt 6.11 deps headers only

    The Windows half of this issue is closed on master. #2969 (5e25ac58) is in this tree and both Windows app builds are green, so the obs-qsv11.c.h C4310/C2220 residual the last comment was waiting on is gone.

    #2970's frontend-api ratchet is verified, not just PR-green. e2782b4ac is the commit that puts obs-frontend-api on -Wconversion;-Wsign-conversion;-Wfloat-conversion, and PR CI never compiles that library with the app configure β€” the Ubuntu, Flatpak and both Windows app builds above do, and all four are green. So this ratchet does not repeat the #2938 shape (a target turned on with unconverted sources behind a lane PR CI does not build).

    What is still red is only the escalated decision. Build 🧱 / macOS 🍏 (arm64) job 123830620422 stops on:

    implicit conversion changes signedness: 'int' to 'quintptr'  (qversiontagging.h:80, : symbol(sym), version(currentVersion))
    implicit conversion changes signedness: 'Int' to 'int'        (qnamespace.h:1926,1930)
    implicit conversion changes signedness: 'int' to 'Int'        (qnamespace.h:1926,1930)
    implicit conversion changes signedness: 'const int' to 'unsigned int' (qnamespace.h:1935)
    

    every one inside .deps/obs-deps-qt6-2026-10-25-universal parsed into the frontend.signal-posix unity group. That is #2950's open Decision needed: (mark the app's .deps includes SYSTEM), unchanged by this tick; there is no first-party conversion to write.

    One honest gap in the table: I started a duplicate scheduled.yaml dispatch on the same ref before finding the one above, and the concurrency group cancelled both runs, so macOS 🍏 (x86_64), Analyze πŸ”¬ / macOS 🍏 (clang-analyze) and Fast Gate ⚑ ended cancelled in this run and carry no evidence either way. The arm64 build reaching the deps headers after compiling every first-party unity group is the same signal those jobs gave on 43af74187.

    PR #2971 (ExtraBrowsersModel.cpp.hpp:190) is green and queued.

  19. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    The macOS half now has its fix on master: #2979 (b0f2e8e3a, 04:21 UTC) keeps the frontend's -Wsign-conversion opt-in off the Darwin TUs, which is the #2950 decision (option B) that was the last thing keeping Build 🧱 / macOS 🍏 (arm64), (x86_64) and Analyze πŸ”¬ / macOS 🍏 red.

    It was green on the branch across five lanes (run 40996937748) and is now re-running on master: scheduled.yaml dispatch 41002744398 on b0f2e8e3a. That run's Ubuntu, Flatpak, Windows x64/arm64, macOS arm64/x86_64 and clang-analyze jobs are this tracker's acceptance list; Linux, Flatpak and Windows were already green at e2782b4ac. I will close here with the verdict once the run finishes, and the only follow-up this leaves is #2989 (restoring the Unix-side ratchet on Darwin later), not a red lane.

  20. zackees commented on Oct 30, 2026

    @zackees
    MemberAuthor

    Every app lane this issue was filed for is green on master, so the tracker closes.

    scheduled.yaml dispatch 41002744398 on master b0f2e8e3a (#2979):

    Lane Result
    Build 🧱 / Ubuntu 🐧 (OBS-Studio-Rust) success
    Build 🧱 / Flatpak πŸ“¦ success
    Build 🧱 / Windows πŸͺŸ (x64) and (arm64) success
    Build 🧱 / macOS 🍏 (arm64) and (x86_64) success
    Analyze πŸ”¬ / macOS 🍏 (clang-analyze) success

    The red set that opened this issue β€” the 63 unconverted frontend files, ExtraBrowsersModel, WhatsNewInfoThread, update-helpers, PluginModuleLoader_MacOS, the frontend-tools/scripts.cpp.hpp pair (#2968) and the obs-qsv11 C4310 regression (#2969) β€” is gone from every lane. The last piece was macOS: #2979 keeps the frontend's -Wsign-conversion opt-in off the Darwin TUs, which is #2950's option B, because those lanes stopped inside Qt 6.11's own headers rather than in obs sources.

    Remaining follow-ups, none of them a red lane:

    Nothing else on the app-lane board is red. Closing.

  21. moved this from In progress to Done in obs-rust Multiviewon Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0Red master or broken release: drop everything (8 h claims)bugSomething isn't workingsize:LSeveral days

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions