Data and AI struggles

1,855 problems · 352 companies

LLM apps

RAG on GitHub returns irrelevant or missing context

10 posts from 8 people7d activeFading, +0 this week

Posts per day

Posts per day10 posts, Sep 3 to Nov 13

The posts behind it

GitHub issuesrun-llama/llama_index · Dennis-nhamOct 25

[Docs] Vietnamese PDF ingestion for RAG — word segmentation before chunking improves retrieval 15%

## Documentation Request: Vietnamese Document Loader Best Practices **Reporter:** [NHAM QUOC HUAN](https://github.com/Dennis-nham) · [NLP Labs Vietnam](https://github.com/nlp-labs-vietnam) We ingest Vietnamese solar technical PDFs (MOIT/EVN) for our RAG advisory pipeline. Key...

1 replies
GitHub issuesvercel/next.js · vjeuxOct 13

Turbopack: with `turbopackFileSystemCacheForBuild` a cold `next build` of a large App Router app is 2.1–2.6× slower (single-threaded aggregation-graph phase) and the 15–21 GB cache is mostly chunk-group dependency edges

**Summary.** On a large App Router application, leaving Next 16's filesystem cache for builds on (`experimental.turbopackFileSystemCacheForBuild`, the default) makes a cold `next build` - one that starts with an empty cache directory, which is every CI build that does not...

GitHub issuescrewAIInc/crewAI · lorenzejayOct 13

[FEATURE] Implement a standard-library JSONL RAG loader

## Python PR scope Add a JSONLLoader through BaseLoader/LoaderResult using Python's json module. Preserve line order and useful scalar metadata without turning JSON values into Python repr strings. **Difficulty:** easy. **Allocation index:** #8118. **Project:** #8119. ## Cohort...

2 replies
GitHub issuescrewAIInc/crewAI · lorenzejayOct 13

[FEATURE] Integrate notebook discovery and chunking with RAG ingestion

## Python PR scope Wire the read-only notebook loader into DataType and .ipynb discovery so notebooks can be added through the regular RAG API. **Difficulty:** medium. **Allocation index:** #8118. **Project:** #8119. ## Cohort allocation This ticket is reserved for...

GitHub issuescrewAIInc/crewAI · lorenzejayOct 13

[BUG] Preserve scalar loader metadata during RAG ingestion

## Python PR scope Fix the reproduced loss of LoaderResult.metadata in RAG.add(). Current code initializes each chunk's metadata from only caller-supplied metadata, dropping loader fields such as JSON format/type/size. **Difficulty:** easy. **Allocation index:** #8118....

1 replies
Redditr/LangChain · u/SeaAstronomer9044Oct 11

Before shipping a RAG retrieval change, do you know which queries might lose evidence?

...experience reinforced something important:. A benchmark can be reproducible and still fail to measure the same definition of success across systems.. What I'm offering now. I'm testing a narrowly scoped independent RAG retrieval audit for teams preparing a release or...

Redditr/RAG · u/Delicious_Pipe_1326Sep 30

Document currency in RAG: how do you tell which version still applies?

New to the forum. I’m working with a small, messy set of policy, project and assurance documents. I’ve reviewed quite a few GitHub RAG projects, but haven’t found one that really tackles whether a source still applies in a mixed collection like this.. Finding a relevant passage...

Redditr/RAG · u/Puzzleheaded_Bad_1Sep 25

Graph Rag and databases just got smarter-and dangerously fast

...heavy agentic capabilities that just slow existing ones down-someone just bypassed the bottleneck using System 1 models Laya and Jev.. Introducing a database-agnostic Agentic GraphRAG framework using swappable System 1 models (local Laya / cloud Jev). It acts as a plug-and-play...

GitHub issuesBerriAI/litellm · giladk1221Sep 22

[Feature]: Add Microsoft Web IQ as a native search provider

### Check for existing issues - [x] I searched existing issues and pull requests for `WebIQ` and `Web IQ` and found no matching request ### The Feature Add Microsoft Web IQ as a native search provider, selectable with `search_provider: webiq`, for the Search API and the existing...

GitHub issuesvercel/next.js · agentHitsSep 3

Turbopack panics in ModuleGraphImportTracer: 'entered unreachable code: there must be a path to a root' (module_graph/mod.rs:750)

### Link to the code that reproduces this issue https://github.com/agentHits/next-prerender-workstore-reproduction ### To Reproduce 1. Clone reproduction repository: 2. Run a cold static export build without `experimental.inlineCss: true`: 3. On projects with standalone output...

1 replies

Companies and products named

10 posts
2 posts
1 post
About this problem

Evidence

10 posts from 8 people in 6 places, about 1 a week over 53 days. Mostly on crewAIInc/crewAI, vercel/next.js, r/RAG. Tools named alongside: Vercel, LangChain, LlamaIndex.

Frustration Frustration 0 of 3· Seen on GitHub issues, Reddit

How it was grouped

Posts that state a pain and match the "rag-retrieval" rule about GitHub. First post Sep 3, 2026, latest Oct 25, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

RAG retrieval returns irrelevant or missing context

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

RAG on LangChain returns irrelevant or missing context

8 posts from 7 people on Reddit, GitHub issues, Stack Overflow.

RAG on Anthropic returns irrelevant or missing context

5 posts from 5 people on GitHub issues, Reddit.

RAG on LlamaIndex returns irrelevant or missing context

5 posts from 5 people on GitHub issues.

RAG on Claude returns irrelevant or missing context

4 posts from 4 people on GitHub issues, Reddit.

RAG on vLLM returns irrelevant or missing context

3 posts from 3 people on GitHub issues.

RAG on OpenAI returns irrelevant or missing context

3 posts from 3 people on GitHub issues.

RAG on PyTorch returns irrelevant or missing context

3 posts from 3 people on GitHub issues, Mastodon.

RAG on Llama returns irrelevant or missing context

3 posts from 2 people on Stack Overflow, Reddit.

RAG on Qdrant returns irrelevant or missing context

3 posts from 2 people on GitHub issues.

RAG on Chroma returns irrelevant or missing context

3 posts from 3 people on GitHub issues.

RAG on SQL Server returns irrelevant or missing context

2 posts from 2 people on Reddit. Unverified.

Other GitHub problems

GitHub outages and slowdowns disrupt work

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

Trouble with GitHub plugin

Top post: "Scheduling queue: gated pod group is requeued on events its gating plugin's QueueingHint skips", one of 6 posts from 5 people on GitHub issues.

Trouble with GitHub next

Top post: "Next Image component fails when a relative src redirects to an external image", one of 20 posts from 18 people on GitHub issues, Reddit.

Trouble with GitHub check

Top post: "E2E testing: check for goroutine leaks", one of 16 posts from 8 people on GitHub issues.

GitHub vulnerabilities are hard to triage and patch

13 posts from 12 people on GitHub issues, Glyph Ibis, Hacker News.

GitHub lock-in makes switching costly

13 posts from 11 people on GitHub issues.

Trouble with GitHub test

Top post: "Remove TestContext from test/integration/util and use ktesting.TContext instead", one of 12 posts from 8 people on GitHub issues, Reddit.

GitHub dependency conflicts break installs

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

GitHub rate limits and usage caps block work

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

Migrating to or off GitHub is slow and risky

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

GitHub deprecations force unplanned migrations

10 posts from 9 people on GitHub issues, Reddit.

Trouble with GitHub server

Top post: "API Server Write Throughput: Reduce Write Allocations", one of 9 posts from 8 people on GitHub issues, Reddit.

History

Momentum went from steady to fading.

Nov 1, 2026

Momentum went from fading to steady.

Oct 28, 2026

Momentum went from rising to fading.

Oct 20, 2026

Momentum went from steady to rising.

Oct 19, 2026

Momentum went from rising to steady.

Oct 18, 2026

Momentum went from steady to rising.

Oct 17, 2026

Momentum went from fading to steady.

Oct 15, 2026

Momentum went from steady to fading.

Oct 7, 2026

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

Oct 6, 2026

Momentum went from fading to steady.

Oct 6, 2026

Momentum went from steady to fading.

Oct 2, 2026

First seen with 2 posts.

Sep 28, 2026