Data and AI struggles

1,730 problems · 342 companies

LLM apps

Trouble with LlamaIndex default

3 posts from 3 people3d activeFading, +0 this week

Posts per day

Posts per day3 posts, Aug 30 to Nov 9

The posts behind it

GitHub issuesrun-llama/llama_index · yifanxiong272Nov 1

[Bug]: `ToolOutput.__init__` declares `raw_input=None` as its default, but leaving it out fails validation

### Bug Description `ToolOutput.__init__` has the signature `raw_input: Optional[Dict[str, Any]] = None` and passes the value on, but the field is `raw_input: Dict[str, Any]`, so the default is rejected. A `ToolOutput` built without `raw_input`, for example in a `FunctionTool`...

1 replies
GitHub issuesrun-llama/llama_index · chrikrahSep 28

[Bug]: max_iterations=0 is silently replaced by the default 20

### Bug Description `max_iterations=0` is silently replaced by the default of 20, so a run that asks for no iterations executes tools and answers normally. `BaseWorkflowAgent._init_context` reads the value with `or`: `0` is falsy, so it never reaches the store....

2 replies
GitHub issuesrun-llama/llama_index · Gracy769Aug 30

[Bug]: `Dispatcher.__init__` and model fields use mutable default arguments (`[]`)

### Bug Description In `llama_index_instrumentation/dispatcher.py`, the `Dispatcher` class contains mutable default arguments in both its Pydantic `Field` declarations and its `__init__` constructor: 1. **Pydantic Model Fields** (lines 68-73): Using `default=[]` rather than...

2 replies

Companies and products named

3 posts
About this problem

Evidence

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

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about LlamaIndex with no known issue, sharing the word "default". First post Aug 30, 2026, latest Nov 1, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

Other LlamaIndex problems

RAG on LlamaIndex returns irrelevant or missing context

5 posts from 5 people on GitHub issues.

LlamaIndex users keep filing bugs

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

LlamaIndex upgrades break working setups

17 posts from 10 people on GitHub issues.

LlamaIndex fails to return valid structured output

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

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.

Experiments on LlamaIndex are hard to reproduce and track

3 posts from 3 people on GitHub issues.

LlamaIndex lock-in makes switching costly

3 posts from 3 people on GitHub issues.

Trouble with LlamaIndex events

Top post: "CBEvent assigns generated uuid to self.id instead of self.id_, so events without an id all share id_=", one of 3 posts from 3 people on GitHub issues.

LlamaIndex integrations break or are missing

2 posts from 2 people on GitHub issues. Unverified.

History

Momentum went from steady to fading.

Nov 8, 2026

First seen with 3 posts; the top post now: "max_iterations=0 is silently replaced by the default 20".

Nov 6, 2026