[Issue Backlog] Backlog Analysis - February 27, 2026 #8790
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-03-06T00:20:39.565Z.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Backlog Analysis - 2026-02-27
Executive Summary
Issues Recommended for Closure
After careful review, one issue can be safely closed:
Critical Soundness Bugs (High Priority)
These issues represent potential correctness problems and should be prioritized:
#8185 - Incorrect model in mixed FP/Real logic triggered by extra string constraint
src/smt/theory_str.cpp,src/smt/theory_fpa.cpp, proof generation:produce-proofs trueis set with mixed FP/Real logic plus string constraints#8194 - Incorrect model with
:produce-proofs trueinvolving String Theory and UFsrc/smt/theory_str.cpp, proof infrastructure#8023 - Soundness issue in string logic
src/smt/theory_str.cpp)str.replace,str.indexofhandlingunsat, cvc5 returnssatwith valid modelstr.replaceoperations#8740 - Z3 Regression: solver.check() returns 'unknown' instead of 'sat'
unknownon satisfiable constraints that 4.15.4 solves correctlysat#2650 - Incorrect result in NRA formula 2
#7990 - Wrong verdict with
(set-option :sat.smt true)#7841, #7842 - Incorrect models for QF_SLIA
#7730 - Spacer returns
satinstead of expectedunsatPerformance Regressions Needing Attention
#7502 - Regression with arith.solver=6
src/smt/theory_arith*)arith.solver=6, investigate rlimit accounting differences#8019 - Massive performance regression in 4.15.4.0 due to lock contention
#7991 - Infinite loop/performance regression in Z3 4.15.3
#7951 - Another seemingly infinite loop
#7800 - Memory and compute regression when upgrade to 4.15.3
#7735 - Memory and time blow-up with z3 4.15.2
Pattern: Multiple performance regressions introduced in 4.15.x series, suggesting a systemic change that needs investigation.
API and Binding Issues
#6512 - NodeJS process won't stop after using 'solve' or 'solver.check()'
#7684 - OCaml bindings don't install with cmake build system
src/api/ml/CMakeLists.txt#7687 - Inconsistent results in CLI and Z3Py API
String Solver Issues (Component Focus)
Multiple string solver issues suggest this component needs focused attention:
str.replace/str.indexof:produce-proofs trueinvolving String Theory and UF #8194: Incorrect model with proof generation (UF + String)QF_SLIA#7841: Incorrect model for QF_SLIARecommendation: Systematic audit of string solver, particularly:
str.replace,str.indexof,str.substraxiomsNotable Long-Standing Issues
Duplicate Clusters (From Previous Analysis)
Based on previous runs:
Issues Needing More Information
Recommendations for Maintainers
Immediate Priority: Address soundness bugs (Incorrect model in mixed FP/Real logic triggered by extra string constraint #8185, Incorrect model with
:produce-proofs trueinvolving String Theory and UF #8194, Soundness issue in string logic #8023, Z3 Regression: solver.check() returns 'unknown' instead of 'sat' #8740):produce-proofs trueinvolving String Theory and UF #8194 both involve proof generation + strings - likely related4.15.x Regression Investigation: Multiple performance regressions in 4.15.x series
String Solver Focus: 7+ issues point to string solver needing attention
Build System Issues: CMake OCaml bindings (OCaml bindings don't install with cmake build system #7684)
Close #7958: Package distribution question already answeredAutomated by Issue Backlog Processor - Last run: 2026-02-27 - Runs every 2 days
Beta Was this translation helpful? Give feedback.
All reactions