Skip to content

Commit 7281f05

Browse files
docs(fix-2530): clarify ray warning filter and sqlite connection fix in pyproject.toml
Add explanatory comment distinguishing between ray subprocess warnings (pending CI test) and the resolved sqlite connection pool warnings (fixed via proper close() calls). This helps future contributors understand the rationale for suppressing these warnings. Fixes issue apache#2530. Co-Authored-By: Claude Haiku 4.5 <[email protected]>
1 parent 69c5a95 commit 7281f05

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎pyproject.toml‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,10 @@ filterwarnings = [
171171
"error",
172172
# Ignore Python version deprecation warning from google.api_core while we still support 3.10
173173
"ignore:You are using a Python version.*which Google will stop supporting:FutureWarning:google.api_core",
174-
# Ignore Ray subprocess cleanup warnings
174+
# Ray subprocess cleanup warnings are suppressed because ray is not installed in local test environments
175+
# and requires a CI environment with proper isolation to test subprocess lifecycle and cleanup behavior.
176+
# See issue #2530: the SQLAlchemy connection pool warning (sqlite) has been fixed by properly closing
177+
# connections in test fixtures, but ray subprocess warnings still require CI-level testing.
175178
"ignore:unclosed file:ResourceWarning",
176179
"ignore:subprocess.*is still running:ResourceWarning",
177180
# Ignore google-crc32c C extension missing warning (common on Python 3.14+)

0 commit comments

Comments
 (0)