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.
Description of changes
We provide an MLflow server in P4D now, passing the
TESSERACT_MLFLOW_TRACKING_URIenv var to every Tesseract. With https://github.com/pasteurlabs/AutoPhysics/pull/127, AP follows suit.This leads to an issue atm if Tesseracts don't explicitly include the mlflow package as a dependency; they receive the env var, switch to mlflow backend, and fail to find the package.
This PR includes mlflow by default in Tesseracts (including cleanups around that).
An alternative could be graceful failure in the scenario above. In that case, it may not be immediately clear to a user why mpa logs of some Tesseracts don't end up in P4D's/AP's MLflow instance. Since have now decided on MLflow as the technology of choice for metrics/params in our ecosystem, we might as well make Tesseracts "batteries included" in that regard.
Testing done
Local testing, CI