question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[SETUP-BUG] Pinned requirement of alembic version getting old

See original GitHub issue

Thank you for submitting an issue. Please refer to our issue policy for information on what types of issues we address.

Please fill in this installation issue template to ensure a timely and thorough response.

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian
  • MLflow installed from (source or binary): Source
  • MLflow version (run mlflow --version): It would be 1.15.0
  • Python version: 3.7.9
  • Exact command to reproduce: pip install mlflow or poetry add mlflow

Describe the problem

I would like to install MLflow for our project. This project has as a dependency that the version of alembic is 1.4.2. I have seen that the requirements for MLflow’s alembic are <=1.4.1 (due to #3363). Since future projects with other packages are likely going to need higher alembic versions it would be nice to remove this limiting requirement. Maybe the issue of failing installs was fixed in higher alembic versions already.

Other info / logs

Because mlflow (1.15.0) depends on alembic (<=1.4.1) 
and no versions of mlflow match >1.15.0,<2.0.0, mlflow (>=1.15.0,<2.0.0) requires alembic (<=1.4.1).

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:6
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
amenckcommented, Dec 8, 2021

Is there any plan to address this? We have included mlflow as a requirement in some of our projects, which has limited us to using alembic 1.4.1. In practice I’m sure it would be fine to upgrade to a more recent version and just run the code, since we only use the client and definitely are not interacting with a DB via mlflow… however, since we have mlflow list in our, we would end up getting a conflict with alembic if we tried to update past 1.4.1.

At a broader level, it seems suboptimal that a library which we are using simply as a client has a requirement which involves DB interaction. Ideally, it would be great if there were a way to skip this entirely, since our use of mlflow does not involve any DB interaction.

0reactions
dbczumarcommented, Dec 6, 2022

Fortunately, https://github.com/mlflow/mlflow/pull/5249 has addressed this issue. Thank you for using MLflow!

Read more comments on GitHub >

github_iconTop Results From Across the Web

[SETUP-BUG] Pinned requirement of alembic version ...
Open source platform for the machine learning lifecycle - [SETUP-BUG] Pinned requirement of alembic version getting old · mlflow/mlflow@d83d69d.
Read more >
Tutorial — Alembic 1.9.0 documentation
Whatever is here is used to generate new files within versions/ . This is scriptable so that the structure of each migration file...
Read more >
python - Undo last Alembic migration
Assuming that you only want to go back one revision, use alembic downgrade with a relative migration identifier of -1: alembic downgrade -1....
Read more >
Safely Test and Apply Changes to Your Database
Safely Test and Apply Changes to Your Database: Getting Started with Alembic. Version control your database with this simple Python tool.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found