[repo-status] Daily Repo Status — May 5, 2026

[github-actions]

🌟 Daily Status Report — May 5, 2026

Good morning, team! Here's a snapshot of what's happening in microsoft/msphpsql today.

---

🚀 Latest Release

v5.13.1 shipped on April 30 — a solid patch release with 5 important fixes:

• 🔒 Access token identity no longer leaks across pooled connections
• ⚙️ Prepared statements with triggers/SET NOCOUNT OFF no longer silently fail
• 🐛 Fatal error fixed on re-executing multi-result-set prepared statements
• 🛠️ sqlsrv_errors() now returns proper errors after failed connections
• 📦 Binary streams are no longer invalidated when their statement goes out of scope

Install: sudo pecl install sqlsrv-5.13.1 / sudo pecl install pdo_sqlsrv-5.13.1

---

🔀 Active Pull Requests (4 open)

PR	Title	Status
#1609	Update test matrix: Ubuntu 24.04 + SQL Server 2025	✅ Ready — opened today
#1600	Fix: Don't call SQLCancel after SQLMoreResults error	✅ Ready for review
#1593	Add SQLSRV_ENCODING_UTF8_VARCHAR for UTF-8 collations	🔬 Draft — awaiting review
#1500	Add fetch_bignumeric attribute	🔬 Draft — older, community PR

🌟 Highlight: PR #1609

Modernizes the CI pipeline to Ubuntu 24.04 and SQL Server 2025 — keeping the test matrix fresh and ensuring we validate against the latest Microsoft stack.

🔥 PR #1593 — UTF-8 VARCHAR Encoding

A significant feature addition that adds SQLSRV_ENCODING_UTF8_VARCHAR (value 65002), enabling direct VARCHAR binding for UTF-8 collation columns. This prevents implicit type conversions that were causing index scans instead of seeks — a real performance win for apps using _UTF8 collations.

---

📝 Recent Commits (last 2 weeks)

Date	Change
May 3	✅ Merged daily-repo-status agentic workflow
Apr 24	🔒 Added DevSkim and Cppcheck CI workflows for PR checks
Apr 24	🐛 Fixed test output.py to correctly detect .diff failures
Apr 21	🔒 Resolved 10 CodeQL SM02986 char*/wchar_t* cast warnings

---

🐛 Open Issues Spotlight

Issue	Summary
#1540	⚠️ Exponential slowdown with 400+ query parameters — performance regression
#1587	🔤 UTF-8 encoding sends NVARCHAR instead of VARCHAR — addressed by PR #1593
#1599	🔁 Incorrect SQLMoreResults return value — addressed by PR #1600
#1594	🔒 Buffer passed to SQLSetConnectAttrW used after function return
#1573	🐧 Linux: driver forces libssl/libcrypto load → deadlock with pre-loaded OpenSSL
#1537	📦 Add PIE (Position Independent Executable) support

---

✅ Actionable Next Steps

1. Review & merge PR #1609 — low-risk CI upgrade, ready to go 🟢
2. Review PR #1600 — important fix for SQLCancel behavior in batch errors
3. Prioritize issue #1540 — exponential slowdown with many params affects production workloads
4. Investigate issue #1594 — use-after-free on connection attribute buffer is a memory safety concern
5. Complete review of PR #1593 — the UTF-8 VARCHAR encoding feature has a reviewer already assigned
6. Triage issue #1573 — OpenSSL deadlock on Linux is a reliability issue for containerized deployments

---

📊 Health Summary

Metric	Count
Open issues	8 (shown)
Open PRs	4
Draft PRs	2
Latest release age	5 days
Recent commits (2 weeks)	5

The project is in excellent health 💪 — fresh release out the door, active CI improvements, and meaningful feature work in progress. Keep up the momentum!

---

🤖 Auto-generated by the daily-repo-status agentic workflow

Generated by Daily Repo Status · ● 154.3K · ◷

[jahnvi480]

@sumitmsft This is quite interesting!!
I have one doubt on what basis does it give "Actionable Next Step"?

[sumitmsft]

@sumitmsft This is quite interesting!! I have one doubt on what basis does it give "Actionable Next Step"?

The "Actionable Next Steps" come entirely from the LLM's interpretation of the repo data it gathers, at this time there's no rule engine, no scoring algorithm, and no curated playbook. We can change this.

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #1612

View newer issue

---

This action was performed automatically by the Daily Repo Status workflow.