Data and AI struggles

1,512 problems · 320 companies

DevOps and infra

MLflow permissions are confusing and error-prone

3 posts from 3 people3d activeRising, +2 this week

Posts per day

Posts per day3 posts, Sep 7 to Nov 3

The posts behind it

GitHub issuesmlflow/mlflow · fferegrinoOct 30

[BUG] basic-auth: `GetWorkspace` returns 403 for non-admins because its validator is never found

### 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...

2 replies
GitHub issuesmlflow/mlflow · MrGolnOct 29

[BUG] REST stores hide the server's error message on 5xx responses ("too many 500 error responses")

...`mlflow/deployments` passes it too. With this change the repro raises `INTERNAL_ERROR: Unable to fetch model from model URI source artifact location 'models:/m-doesnotexist'.Error: Logged model with ID 'm-doesnotexist' not found.`, with both 7 and 0 retries; the number of...

2 replies
GitHub issuesmlflow/mlflow · mkBGDSep 7

[BUG] basic-auth: fail-closed authorization denies `GET /` (the web UI) to every user without the server-wide `is_admin` flag

> [!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...

1 reactions2 replies

Companies and products named

3 posts
3 posts
1 post
1 post
About this problem

Evidence

3 posts from 3 people in 1 place, about 1 a week over 54 days. Mostly on mlflow/mlflow. Tools named alongside: GitHub, PyPI, PostgreSQL, Docker.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "permissions" rule about MLflow. First post Sep 7, 2026, latest Oct 30, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Permissions and IAM are confusing and error-prone

29 posts from 29 people on GitHub issues, Reddit, Community forums.

AWS permissions are confusing and error-prone

10 posts from 10 people on Reddit, GitHub issues, Hacker News.

Kubernetes permissions are confusing and error-prone

9 posts from 5 people on Mastodon, Bluesky, Reddit.

PostgreSQL permissions are confusing and error-prone

5 posts from 5 people on GitHub issues, Hacker News.

GitHub permissions are confusing and error-prone

4 posts from 4 people on GitHub issues, Reddit.

Docker permissions are confusing and error-prone

4 posts from 4 people on GitHub issues, Stack Overflow.

Gemini permissions are confusing and error-prone

3 posts from 3 people on Community forums, GitHub issues.

DuckDB permissions are confusing and error-prone

3 posts from 3 people on GitHub issues.

ChatGPT permissions are confusing and error-prone

2 posts from 2 people on GitHub issues. Unverified.

BigQuery permissions are confusing and error-prone

2 posts from 2 people on GitHub issues. Unverified.

Claude permissions are confusing and error-prone

2 posts from 2 people on Reddit. Unverified.

Google Cloud permissions are confusing and error-prone

2 posts from 2 people on GitHub issues. Unverified.

Other MLflow problems

MLflow upgrades break working setups

13 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 trace

Top post: "Flagging a Trace for Review Auto Closes Overlay and Toast Notification", one of 6 posts from 5 people on GitHub issues.

MLflow rate limits and usage caps block work

5 posts from 5 people on GitHub issues.

Experiments on MLflow are hard to reproduce and track

3 posts from 3 people on GitHub issues.

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.

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 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 hits connection, locking and scaling limits

4 posts from 4 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.

Trouble with MLflow artifact

Top post: "Test requirements: test_http_artifact_root_uses_presigned_only_split_server 403 recurs after #27212 was closed", one of 3 posts from 3 people on GitHub issues.

History

First seen with 3 posts.

Nov 3, 2026