Problemsby GlyphMLflow upgrades break working setups
13 posts from 12 people10d activeFading, +0 this week
Posts per day
The posts behind it
Nightly: `setup.sh` E2E server fixture exhausts its startup wait
> Filed manually from an investigation of the scheduled Test requirements run. ### Summary Four tests errored because the shared `mlflow_server` fixture exhausted its readiness wait while the MLflow server was still starting. The fixture makes 60 attempts with a 0.25-second...
[BUG] Trace total_tokens is 0 when a span reports only input tokens
### PR policy - [x] I understand that PRs for this issue are closed automatically unless a maintainer has applied the `ready` label, the issue isn't assigned to someone else, and no open PR already links it. - [x] I understand a triage bot may open a PR for this issue...
[BUG] Basic auth: a role's DENY on a registered model stops applying after the model is renamed
...Linux 2023) - **Python version**: 3.12.13 - **Database**: SQLite ### Describe the problem With basic auth enabled, a role that grants `READ` on every registered model (`*`) and `DENY` on one model stops denying that model once it is renamed. The caller can then read it under its...
[BUG] `bedrock:/` judges raise `NotImplementedError: AmazonBedrockProvider does not implement get_endpoint_url` even without `{{ trace }}`
Thanks for #23586, which made judge costs show up in the UI. One side effect: `bedrock:/` judges now fail before they reach Bedrock, also without `{{ trace }}`. ### Issues Policy acknowledgement - [ ] I have read and agree to submit bug reports in accordance with the [issues...
[BUG] Appending to a JSON table converts previously logged string identifiers to numbers
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[BUG] `log_table` mutates image DataFrames and leaves missing image artifacts when reused across runs
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[BUG] search_logged_models status filters never match on the SQL store
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[BUG] mlflow.genai.evaluate fails for scorers that return NumPy scalars (np.bool_, np.int64, ...)
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[BUG] Multipart artifact downloads silently corrupt files when endpoints ignore Range
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[UI-BUG] "Copy link to trace" generates a broken URL missing the `#` fragment, causing a 404
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### MLflow version...
[BUG] `@mlflow.trace` on a generator never ends the span when the consumer stops early (break / close / islice)
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
[BUG] Integer expectation values are returned as floats when using a tracking server
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. **Issues Policy...
[BUG] AI Gateway streaming passthrough calls made via plain REST (no MLflow SDK client) never get mlflow.chat.tokenUsage attached, so trace-level Tokens/Cost stay empty
> [!WARNING] > Before submitting a PR, please make sure that: > - A maintainer has triaged this issue and applied the `ready` label > - This issue has no assignee > - No duplicate PR exists > > PRs not meeting these requirements may be automatically closed. ### Issues Policy...
Companies and products named
About this problem
Evidence
13 posts from 12 people in 1 place, about 2 a week over 56 days. Mostly on mlflow/mlflow. Tools named alongside: GitHub, SQLite, Databricks, pandas.
Frustration Frustration 1 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "breaking-changes" rule about MLflow. First post Sep 8, 2026, latest Nov 2, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
The same problem elsewhere
GitHub upgrades break working setups
87 posts from 75 people on GitHub issues, Hacker News, Stack Overflow.
Upgrades and new releases break working setups
76 posts from 62 people on GitHub issues, Reddit, App Store reviews.
Claude Code upgrades break working setups
67 posts from 60 people on GitHub issues, Hacker News, Reddit.
Codex upgrades break working setups
65 posts from 58 people on GitHub issues, Reddit.
DuckDB upgrades break working setups
37 posts from 28 people on GitHub issues.
Claude upgrades break working setups
35 posts from 34 people on GitHub issues, Reddit, Hacker News.
ClickHouse upgrades break working setups
31 posts from 20 people on GitHub issues.
Anthropic upgrades break working setups
27 posts from 22 people on GitHub issues.
PyTorch upgrades break working setups
26 posts from 21 people on GitHub issues, Reddit.
ChatGPT upgrades break working setups
26 posts from 26 people on GitHub issues, Community forums, App Store reviews.
OpenAI upgrades break working setups
25 posts from 25 people on GitHub issues, Reddit, Community forums.
Open WebUI upgrades break working setups
25 posts from 2 people on GitHub issues.
Other MLflow problems
MLflow users keep filing bugs
Top post: "`mlflow db move-resources` makes existing proxied (`mlflow-artifacts:/`) artifacts of moved experiments", one of 21 posts from 12 people on GitHub issues.
Serving models on MLflow is harder than it should be
15 posts from 14 people on GitHub issues.
Trouble with MLflow list
Top post: "`users/list` returns users from other workspaces when workspaces are enabled", one of 7 posts from 6 people on GitHub issues.
Trouble with MLflow trace
Top post: "Flagging a Trace for Review Auto Closes Overlay and Toast Notification", one of 6 posts from 5 people on GitHub issues.
Trouble with MLflow traces
Top post: "Add a typed client API to submit Issue Detection for traces", one of 6 posts from 4 people on GitHub issues.
MLflow rate limits and usage caps block work
5 posts from 5 people on GitHub issues.
MLflow vulnerabilities are hard to triage and patch
4 posts from 4 people on Glyph Ibis.
Trouble with MLflow metric
Top post: "log_metric and log_metrics replace timestamp=0 with current time", one of 4 posts from 3 people on GitHub issues.
MLflow hits connection, locking and scaling limits
4 posts from 4 people on GitHub issues.
MLflow permissions are confusing and error-prone
3 posts from 3 people on GitHub issues.
Experiments on MLflow are hard to reproduce and track
3 posts from 3 people on GitHub issues.
Trouble with MLflow evaluation
Top post: "Cancel button in the evaluation dataset Add record panel does nothing", one of 3 posts from 2 people on GitHub issues.
History