dont check for tracking uri when running mlflow offline #146
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.
The old behavior when running offline with the default tracking uri ('???') would cause a crash. So now tracking uri isnt checked when running offline
My understanding is there is no reason to check tracking uri when running offline because tracking_uri is provided later if the run is synced to mlflow.
One use case for running offline without a tracking uri would be for external vendors benchmarking anemoi. They could use the mlflow offline logging to analyse GPU utilization etc.