Experiments on LlamaIndex are hard to reproduce and track

MLOps2 posts from 2 people2d active+11 post in the last 7 days, 0 the 7 days before (steady)Unverified

Posts per day2 posts, Sep 19 to Oct 4

The posts behind it

2, newest first

Post	Where	Date
[Bug]: SimpleFileNodeParser ignores custom id_func for supported file types## Bug Description Setting id_func on SimpleFileNodeParser has no effect when it delegates to MarkdownNodeParser, JSONNodeParser or HTMLNodeParser. The nodes get the child parser's default UUIDs. The fallback path already uses the custom callback. The callback should receive the...run-llama/llama_indextakagibit18	run-llama/llama_indextakagibit18	Oct 22 days ago
[Bug]: stream_structured_predict / astream_structured_predict raise UnboundLocalError instead of yielding nothing when the partial stream is empty### Bug Description `LLM.stream_structured_predict` (llama-index-core/llama_index/core/llms/llm.py:461) and its async twin `LLM.astream_structured_predict` (llm.py:539) emit their terminal instrumentation event with the loop variable, after the loop that binds it: The async...run-llama/llama_indexBlueX888	run-llama/llama_indexBlueX888	Sep 192 weeks ago

Companies and products named

Company or product	Posts naming it
LlamaIndex	2

About this problem

Evidence

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

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "ml-reproducibility" rule about LlamaIndex. First post Sep 19, 2026, latest Oct 2, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere

Posts per day

The posts behind it

Companies and products named

Rising problems by email