sqlmap/lib
Piyush satyarthi cb5216564a
Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181)
Python 3.13+ reports sqlite3 connections that are garbage collected
without being closed. The unit tests print a run of
"ResourceWarning: unclosed database" lines on Linux/CPython 3.14:

- SQLAlchemy.close() only returned its connection to the engine's
  pool, so the underlying DBAPI connection (e.g. sqlite3 for
  '-d sqlite://...') stayed open. Dispose the engine on close.
- vulnTest() used "with sqlite3.connect(...)", which commits but does
  not close the connection. Use contextlib.closing().
- test_multibit and test_sqlalchemy never closed what they opened.

Co-authored-by: PiyushSatyarthi <244159432+PiyushSatyarthi@users.noreply.github.com>
2026-11-12 09:46:10 +01:00
..
controller Fixes #6163 2026-10-29 14:15:37 +01:00
core Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181) 2026-11-12 09:46:10 +01:00
parse Implements #6177 2026-11-06 15:31:35 +01:00
request Minor update 2026-11-04 10:20:01 +01:00
takeover
techniques Fixes #6157 2026-10-25 16:29:02 +01:00
utils Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181) 2026-11-12 09:46:10 +01:00
__init__.py