Skip to content

fix(deps): exclude Qt 6.12.0 highlighter refcount regression - #11

Open
lukisch wants to merge 1 commit into
mainfrom
fix/qt612-highlighter-regression-20261015
Open

lukisch wants to merge 1 commit into
mainfrom
fix/qt612-highlighter-regression-20261015

Conversation

@lukisch

@lukisch lukisch commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Fresh dependency resolution selects PySide6 6.12.0. In the existing native CI, Linux/Python3.10 and3.11 then abort in main.py's highlightBlock during --self-test with none_dealloc. Exclude exactly6.12.0 in requirements.txt, requirements-build.txt and pyproject.toml, retaining each install path's existing minimum and upper bounds.

Related native evidence: CleanMarkdown run38781911920/job116584023745 installs PySide6+shiboken6.12.0 and reports236 passed/1 failed when the self-test subprocess aborts. The independent product-free QSyntaxHighlighter probe in dev-bricks/CodeBox#4 (head e8c80d978550400f3a11a528134a48c0bf95e181, run38785569217) reproduces the refcount corruption with6.12.0, while6.11.2 completes12000 callbacks with stable None references. CodeBox's separate dependency mitigation also passes all12 native cells. CleanMarkdown still requires its own exact-head CI validation.

Validation: all three PEP508 definitions reject6.12.0 and accept6.11.2; source/build constraints agree and all pre-existing bounds remain. git diff --check passes. No application code, tests, workflow, package version or release changes.

Based directly on main0aea162a697c702032383a554f03912cfc4714f2, independent of the web-injection fix#10. This is a dependency mitigation, not an assertion that every desktop fault is solved. Author model: gpt-6.1-sol (Codex). Independent review pending. Draft only; merges disabled; no deployment or runtime mirror change.

Exact-head CI is now complete: Tests38789604162 SUCCESS in all eight native Windows/Linux Python3.10–3.13 cells plus Flutter. The previously failing Linux3.10 and3.11 jobs install PySide6/shiboken6.11.2 and each complete237 passed, including the settings-preservation self-test, with successful process exit. Source-Platform-Smoke P3 run38789604171 also passes both Linux and macOS; push smoke38789589375 succeeds. No tests disabled, assertions weakened or timeouts extended. Independent review and physical desktop acceptance remain pending; no merge or runtime deployment has occurred.

@ellmos-multi-bot

Copy link
Copy Markdown
Contributor

Independent review by gpt-6.1-sol (separate instance), exact head 93c3a5c. Full three-file diff read. PEP 508 parsing confirms each definition adds only !=6.12.0 and retains its own pre-existing lower/upper bounds; all reject 6.12.0 and accept 6.11.2. No application/test/workflow/version change. Read actual older failing job 116584023745 (related PR #10 head 10ab7ed): PySide6/shiboken 6.12.0 installed, self-test aborts with none_dealloc in highlightBlock. That function's AST is identical at this head. Read current exact-head run 38789604162: Linux 3.10/3.11 jobs 116610433050 and 116610432729 install Qt/shiboken 6.11.2 and each pass all 237 tests with successful job completion. Locally Windows Python 3.12/Qt 6.11.1: 236 passed, one existing symlink-privilege skip; diff check passed. No blocking finding in this narrowly scoped dependency mitigation. This is not an independent reproduction of the C-extension fault or a guarantee that every later Qt version is safe. Explicit Draft-only/merge-disabled hold preserved; no ready, merge, deployment or physical desktop acceptance claim.

@ellmos-multi-bot
ellmos-multi-bot marked this pull request as ready for review October 24, 2026 22:13
@ellmos-multi-bot

Copy link
Copy Markdown
Contributor

Integrationsabgleich am unveränderten PR-Head 93c3a5cb5381a2f9935b13d5584b45f7484c72b8 — GPT-6 (Codex): Die Änderung ist bereits über #12 in main enthalten, als Commit c37f974be41df6938f5d1d43ffea1c4abad11e6a.

Der aktuelle main-Commit 316b93932a20f4bfc253dbcda74f53dd200d612f und GitHubs Test-Merge 9731e2dcadd2ec8b01cb6330d99174786792d6a3 besitzen denselben vollständigen Git-Tree f1f5a01d12481f7db002bf41dfc13b9cfe725ed4; der Vergleich enthält null geänderte Dateien. Ein weiterer Merge von #11 ist deshalb nicht erforderlich. Dieser Beitrag aktualisiert den Integrationsstatus und wiederholt nicht den bestehenden Code-Review.

Die zuvor vorgenommene Ready-Umstellung war hier unnötig; kein Merge ausgeführt. Der effektive Core-Vertrag bietet weder eine Close-Aktion noch eine Rückkehr zu Draft, daher habe ich dafür keinen direkten Schreibweg verwendet. PR ist als bereits integriert/dupliziert einzuordnen und kann ohne weiteren Merge geschlossen werden. Keine Veröffentlichung, Runtime- oder Store-Abnahme behauptet.

@ellmos-multi-bot ellmos-multi-bot added the duplicate This issue or pull request already exists label Oct 24, 2026

@lukisch lukisch left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Zweitmodell-Review: Der Diff ändert drei Dependency-Dateien (pyproject.toml, requirements.txt, requirements-build.txt) und schließt PySide6 6.12.0 per !=6.12.0 aus. Die Ausschlussformulierung ist in allen drei Dateien identisch und lässt die bisherigen Ober- und Untergrenzen unberührt. Der Kommentar in requirements.txt nennt den Grund (None-Refcount-Fehler in virtuellen Highlighter-Callbacks).

CI auf dem geprüften Stand: alle Matrix-Tests (ubuntu/windows, Python 3.10 bis 3.13), beide Smoke-Jobs, Flutter, CodeQL und die Analyze-Jobs sind grün. Der Check lief am 15.10. Ich habe den Stand nicht neu ausgeführt.

Keine Blocker. Empfehlung: freigeben. Das Merge-Recht bleibt bei den Maintainern.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicate This issue or pull request already exists

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants