Daniel Lok

cc @harupy multipart download is enabled by default right? are there any known instability issues?

@mazer-ai let us know again if upgrading your tracking server doesn't work! cc @harupy for visibility—is the MLflow 3 client meant to be able to interact with MLflow 2 servers?...

yes i believe there can be some issues downgrading if you start logging MLflow 3 artifacts to your server (runs, models), and then downgrade with those artifacts still in the...

Thanks for reporting, this seems to generally relate to rate limiting, which is also tracked in other issues (e.g. #16028)

Mostly LGTM! cc @hubertzub-db in case you'd like to take a look as well. @arnaudh could you run `yarn prettier:fix` inside the `mlflow/server/js` directory to fix the formatting issues? Additionally,...

@arnaudh sorry i missed this! let me re-run the tests and merge if they all pass

@arnaudh looks like some JS tests need updating (`src/experiment-tracking/components/ArtifactPage.intg.test.tsx`), test results are [here](https://github.com/mlflow/mlflow/actions/runs/11103996429/job/31264624851?pr=13232), but you can run it locally with `yarn test src/experiment-tracking/components/ArtifactPage.intg.test.tsx` from the `mlflow/server/js` directory

Hi @haridassaiprakash, if you're looking for documentation, please check out the main docs site at https://mlflow.org/docs/latest/index.html. You might find it easiest to get started with the [Quickstart Guide](https://mlflow.org/docs/latest/getting-started/intro-quickstart/index.html), which introduces...

Thanks for the FR! This sounds reasonable, though implementation wise i guess the reason it's not logged at the moment is that it's not technically an output, and MLflow Tracing...

the test failures should all be unrelated, given that this PR only touches JS files. i'll take a look at this tomorrow