Triage: Open issues with recent activity requiring maintainer action (last 3 months)

[Copilot]

Analysis of all open issues updated since 2025-12-11 to surface ones blocked on maintainer response or pending implementation work.

Findings: 20 issues updated, 9 need action

🔴 Immediate action required

• AT+CIPRECVLEN issue in UDP mode and passive receive mode #994 — AT+CIPRECVLEN/AT+CIPRECVDATA UDP datagram integrity: @ustccw committed to implement new params (datagram_len_report_mode, keep_datagram_integrity) on master this week. Not yet done.
• Unable to secure characteristics with required pairing on NimBLE devices #979 — NimBLE (ESP32-C6) CCC write not triggering encryption/pairing. User confirmed issue 2026-01-26. @XionHsieh1025 has not responded. Waiting 6+ weeks.
• BLE pairing is reoccurring for already paired devices #922 — RPA reconnect broken after MAC rotation on Android. @ustccw acknowledged post-CNY holiday (2026-02-27) but no update. User waiting since 2026-01-06.

🟡 Follow up this week

• Crash when Android connects in a busy BLE environment #921 — BLE crash in high-density RF environment. Debug lib provided 2025-12-25; user hit cert errors building 2026-01-06, got workaround, but no confirmation debug logs were captured.
• SPI-AT documentation has reversed slave status bits #995 — SPI-AT slave status bits reversed in docs. Community contributor acknowledged error 2026-03-04; no PR submitted yet.
• HTTPCLIENT的GET命令是在什么时候关闭链接的? #987 — AT+HTTPCLIENT heap corruption (tlsf.c:330). User sent repro via email 2026-02-07; needs explicit acknowledgment and root cause.

🟢 Can close (stale, no user response)

• BLE MTU size not being respected after pairing on ESP32-C6 #952 — BLE MTU not respected post-pairing: asked to test latest master 2026-01-30, no reply (40+ days).
• How to build a at_spi_master host program on a non-esp32 MCU #975 — SPI master on non-ESP32 MCU: asked for chip model 2025-12-15, no reply (85+ days).

✅ Already resolved / no action needed

#993, #986, #988, #980, #977, #984, #920, #981, #325, #743, #992 — all answered or user self-resolved.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.