You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
air: fall back to MLflow when Bricklens returns no logs for a terminal run
`air logs <run>` printed "No logs available for run <id>. Run terminated
in state SUCCESS" and exited 0 for runs whose logs were fully retrievable:
`air logs --download-to DIR` on the same run returned the complete log.
This happens when Bricklens is enabled for the workspace but never ingested
the run — it answers every request successfully with zero records, yet the
logs are present in MLflow.
The streaming (print) path only fell back to MLflow on errBricklensFeatureDisabled
(gated off / not deployed / persistent failure); an empty-but-successful
Bricklens response was treated as the final answer. The download path already
reads from MLflow, which is why it worked.
Treat "Bricklens served every request but never returned a record" the same
as feature-disabled: hand off to the MLflow fallback, which owns the real
no-logs report and preserves the run-derived exit code. This mirrors the
Python CLI fix (databricks-eng/universe#2366012). Applies to both the terminal
tail and the static (past-retry) view.
Co-authored-by: Isaac
0 commit comments