-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Migrate core MLflow integration from file store to SQLite #8894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Lawson-Darrow
wants to merge
6
commits into
Project-MONAI:dev
Choose a base branch
from
Lawson-Darrow:mlflow-sqlite-migration
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7017510
Migrate core MLflow integration from file store to SQLite
Lawson-Darrow e594111
Fix test_default_sqlite_run_flow run-close ordering
Lawson-Darrow c81c40a
Release SQLite engine in MLFlowHandler.close() for Windows cleanup
Lawson-Darrow 6171526
Release SQLite engines before deleting MLflow test dbs on Windows
Lawson-Darrow e6c76e0
Guard isinstance against dead weakref proxies in _dispose_sqlite_engines
Lawson-Darrow 2daf8a9
Derive artifact location from MLFLOW_TRACKING_URI env var too
Lawson-Darrow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Project-MONAI/MONAI
Length of output: 47
🌐 Web query:
Does SQLAlchemy URL expose get_backend_name() and a database attribute in 1.4 and 2.0?💡 Result:
Yes, the SQLAlchemy URL object exposes both the get_backend_name method and the database attribute in both SQLAlchemy 1.4 and 2.0 [1][2]. Both were formalized as part of the URL object's overhaul in version 1.4, where the URL object was redesigned to be an immutable namedtuple-like structure [3][4]. The get_backend_name method returns the database backend name (the portion of the drivername to the left of the plus sign) [1][2], and the database attribute provides access to the database name specified in the URL [1][2].
Citations:
🏁 Script executed:
Repository: Project-MONAI/MONAI
Length of output: 45
🌐 Web query:
sqlalchemy version pins MONAI supported versions (sqlalchemy) fl monai_algo?💡 Result:
MONAI does not appear to pin SQLAlchemy versions. What I found in MONAI packaging/dependency metadata: - MONAI’s declared install requirements in setup.cfg list torch and numpy, plus many optional dependencies under extras; SQLAlchemy is not present in the shown install_requires or extras list [1][2]. - The MONAI PyPI page describes dependency versioning for major releases and points to requirements*.txt files, but the dependency table excerpt shown there does not include SQLAlchemy [3]. So there is no explicit “sqlalchemy version pin” I can cite from MONAI’s published dependency metadata for the monai/fl client algorithm component (monai_algo.py) either—monai_algo.py itself is code for FL client behavior and does not specify SQLAlchemy dependencies [4]. If you meant “MONAI FL (monai_algo) indirectly depends on SQLAlchemy via another library”, tell me which MONAI version you’re using (e.g., 1.3.0/1.4.0/1.5.x) and your install extras (e.g., monai[all]) and I can trace the transitive dependency chain from that exact lockfile/requirements output.
Citations:
🏁 Script executed:
Repository: Project-MONAI/MONAI
Length of output: 146
🏁 Script executed:
Repository: Project-MONAI/MONAI
Length of output: 45
Narrow the failure mode of
_dispose_sqlite_engines()(SQLAlchemy URL API)get_backend_name()anddatabasein the 1.4/2.0 API, so the current attribute access matches upstream.except Exception:to expected errors (e.g.,AttributeError) or gate withhasattr(url, "get_backend_name")/hasattr(url, "database")so failures aren’t fully swallowed.🧰 Tools
🪛 Ruff (0.15.15)
[error] 208-209:
try-except-passdetected, consider logging the exception(S110)
[warning] 208-208: Do not catch blind exception:
Exception(BLE001)
🤖 Prompt for AI Agents