Data and AI struggles

2,114 problems · 377 companies

LLM apps

LlamaIndex fails to return valid structured output

5 posts from 5 people5d activeFading, +0 this week

Posts per day

Posts per day5 posts, Sep 17 to Nov 21

The posts behind it

GitHub issuesrun-llama/llama_index · anishgurjarOct 15

SelectionOutputParser raises raw KeyError/TypeError on wrong-shaped LLM output

...raises `OutputParserException`, so callers can handle "the model returned something unusable" in one place. I have a small fix with tests and will open a PR.

GitHub issuesrun-llama/llama_index · LaptopminiOct 14

[Bug]: AG-UI router: frontend tool parameters lose their types and enums (everything becomes str)

### Bug Description Tools sent by the client in `RunAgentInput.tools` are rebuilt by `_ag_ui_tool_to_llama_index` (agent.py) as a pydantic model where every property is `str` (required) or `Optional[str]`, and only `description` is kept. `enum`,...

GitHub issuesrun-llama/llama_index · digit50Oct 10

[Bug]: Refine with streaming=True and output_cls returns "Empty Response"

### Bug Description When `Refine` or `CompactAndRefine` (the default `compact` mode) is built with both `streaming=True` and an `output_cls`, the LLM's structured output is thrown away and `synthesize` / `asynthesize` return a plain, non-streaming `Response("Empty Response")`....

GitHub issuesrun-llama/llama_index · 00200200Sep 29

[Bug]: FunctionTool drops postponed annotations, so Context tools and Pydantic params break

### Bug Description `FunctionTool` and `create_schema_from_function` inspect function signatures with `inspect.signature()` and never resolve string annotations. In any module that uses `from __future__ import annotations` (PEP 563), parameter annotations are strings. That...

GitHub issuesrun-llama/llama_index · GYWang1983Sep 17

[Bug]: DashScope FunctionTool conversion drops nested JSON Schema definitions

## Bug description `llama-index-llms-dashscope==0.7.0` corrupts valid nested JSON Schema when it converts a `FunctionTool` for DashScope. `DashScope._convert_tool_to_dashscope_format()` retains only `type` and `properties` from `tool.metadata.get_parameters_dict()`. For Pydantic...

Companies and products named

5 posts
About this problem

Evidence

5 posts from 5 people in 1 place, about 1 a week over 29 days. Mostly on run-llama/llama_index.

Frustration Frustration 2 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "structured-output" rule about LlamaIndex. First post Sep 17, 2026, latest Oct 15, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Models fail to return valid structured output

19 posts from 17 people on GitHub issues.

Claude fails to return valid structured output

15 posts from 12 people on GitHub issues.

OpenAI fails to return valid structured output

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

Anthropic fails to return valid structured output

6 posts from 6 people on GitHub issues.

Codex fails to return valid structured output

6 posts from 3 people on GitHub issues.

LangChain fails to return valid structured output

5 posts from 4 people on GitHub issues.

Model Context Protocol fails to return valid structured output

5 posts from 5 people on GitHub issues, Reddit.

vLLM fails to return valid structured output

5 posts from 5 people on GitHub issues.

Ollama fails to return valid structured output

4 posts from 3 people on GitHub issues.

Gemini fails to return valid structured output

4 posts from 4 people on GitHub issues, Reddit.

Mistral fails to return valid structured output

3 posts from 3 people on GitHub issues.

GitHub fails to return valid structured output

3 posts from 3 people on GitHub issues.

Other LlamaIndex problems

LlamaIndex upgrades break working setups

19 posts from 12 people on GitHub issues.

LlamaIndex users keep filing bugs

Top post: "SQLAlchemyChatStore.delete_message treats positional index as database primary key", one of 13 posts from 8 people on GitHub issues, Stack Overflow.

RAG on LlamaIndex returns irrelevant or missing context

5 posts from 5 people on GitHub issues.

Trouble with LlamaIndex json

Top post: "JSONNodeParser emits empty-text nodes for {} and misreports valid scalar JSON as invalid", one of 3 posts from 3 people on GitHub issues.

Trouble with LlamaIndex returns

Top post: "LegacyOfficeReader returns a Document with text None for a document with no text", one of 3 posts from 3 people on GitHub issues.

LlamaIndex vector search quality is hard to get right

3 posts from 3 people on GitHub issues.

Trouble with LlamaIndex functiontool

Top post: "FunctionTool wraps a returned ToolOutput as a success and drops is_error", one of 3 posts from 3 people on GitHub issues.

LlamaIndex runs out of context on real work

3 posts from 2 people on GitHub issues.

Trouble with LlamaIndex documents

Top post: "MoorchehVectorStore sparse-vector path raises NameError (missing imports, undefined 'documents', ImpotError", one of 3 posts from 3 people on GitHub issues.

Trouble with LlamaIndex default

Top post: "max_iterations=0 is silently replaced by the default 20", one of 3 posts from 3 people on GitHub issues.

Trouble with LlamaIndex documentation

Top post: "The API documentation cannot be used properly and cannot be scrolled to see more content", one of 3 posts from 3 people on GitHub issues.

Experiments on LlamaIndex are hard to reproduce and track

3 posts from 3 people on GitHub issues.

History

Momentum went from steady to fading.

Oct 22, 2026

Momentum went from fading to steady.

Oct 19, 2026

Momentum went from steady to fading.

Oct 17, 2026

Corroborated: 3 or more posts from 2 or more people or places.

Oct 11, 2026

Momentum went from fading to steady.

Oct 11, 2026

Momentum went from steady to fading.

Oct 6, 2026

First seen with 2 posts.

Oct 4, 2026