Data and AI struggles

2,114 problems · 377 companies

LLM apps

Trouble with LlamaIndex json

3 posts from 3 people3d activeFading, +0 this week

Posts per day

Posts per day3 posts, Sep 10 to Nov 21

The posts behind it

GitHub issuesrun-llama/llama_index · SpecstreamaiNov 11

[Feature Request]: Optional base_url for GoogleSearchToolSpec (Google Custom Search JSON API ends January 1, 2027)

### Feature Description An optional `base_url` argument for `GoogleSearchToolSpec`, defaulting to `https://www.googleapis.com/customsearch/v1`, so the tool can call any service that answers in the Custom Search JSON format. `AirweaveToolSpec` takes `base_url: Optional[str] =...

GitHub issuesrun-llama/llama_index · k39139215-gifNov 2

[Bug]: Boundary defect in _marshal_llm_to_json on citation brackets & recursive clobbering in SelectionOutputParser._filter_dict

### Bug Description Two related defects were identified in `llama-index-core` output parsers during automated agent assurance testing: 1. **`_marshal_llm_to_json` Boundary Defect (`llama-index-core/llama_index/core/output_parsers/utils.py` L29-36)**: The extraction logic chooses...

GitHub issuesrun-llama/llama_index · Harsh23KashyapSep 10

JSONNodeParser emits empty-text nodes for {} and misreports valid scalar JSON as "invalid"

### Bug description `JSONNodeParser.get_nodes_from_node` has two edge behaviors that produce silently wrong output: 1. An empty JSON object becomes a node with empty text. `JSONNodeParser().get_nodes_from_documents([Document(text="{}")])` returns one `TextNode` whose `text` is...

1 replies

Companies and products named

3 posts
About this problem

Evidence

3 posts from 3 people in 1 place, about 1 a week over 63 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 "json". First post Sep 10, 2026, latest Nov 11, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

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.

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.

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.

Nov 18, 2026

First seen with 3 posts; the top post now: "JSONNodeParser emits empty-text nodes for {} and misreports valid scalar JSON as invalid".

Nov 16, 2026