Error retrieving pre-indexed documentation.

[colinskow]

Before submitting your bug report

• [X] I believe this is a bug. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that reports the same bug
• [X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows 11
- Continue: latest release
- IDE: VS Code
- Model: Codestral for both main chat and autocompletions
- Embeddings: voyage-code-2 with my own API key

Description

When I type @React or type @docs and select any of the default documentation sites I get the following error, and no context is inserted into the prompts. When I use a custom documentation site that I added myself it works fine.

Error getting context items from docs: Error: No body returned when downloading from S3 bucket

To reproduce

No response

Log output

No response

[nmcostello]

Plus 1 to this issue. We've seen this on a build in Windows.

[mcthesw]

I also encountered this problem

[driverCzn]

I encountered this as well

• OS: Windows 10
• Continue: latest release (v0.8.40)
• IDE: VS Code
• Model: Ollama - llama3 for main chat

Noticed that there was a request to continue-indexed-docs.s3.us-west-1.amazonaws.com:443 when I tried to retrieve the pre-indexed doc and then I got the error Error getting context items from docs: Error: No body returned when downloading from S3 bucket

And this error only shows when I checking some specific docs, e.g. docs.continue.dev, C# Language Reference

[nmcostello]

I would like to elaborate on this issue, we are seeing this in Windows, but seeing a different (maybe simliar) issue on Mac. I was hoping that e7f1f43 would fix this, but no luck.

- OS: MacOS Sonoma 14.5 (Intel)
- Continue: latest pre-release
- IDE: VS Code

Console log output

Error getting context items from docs: Error: connect ETIMEDOUT 52.219.220.194:443

[satya-karthik]

facing the same issue on:

continue version: v0.8.40
VSCODE Version: 1.90.2 (user setup)
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
Date: 2024-06-18T22:34:26.404Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22621

at least provide an option to remove all these pre-built docs. that why we can add them ourselves.

[sestinj]

I believe this has since been resolved—there was a difference in naming scheme that pointed to a non-existent bucket.

Let me know if there's something else going on as well. I don't want to close this issue yet as I think there's a chance that something else is necessary

[blakkd]

Same issue here:

Continue: v0.9.182 (pre-release)
VSCode: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:12.169Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Linux x64 6.5.0-41-generic

Some specific docs can't be retrieved. I've encountered it with Continue several times, and right now with Pytorch. I don't know if the issue is persistant or temporary as I just started using Continue 2 days ago :D

[gizbo]

Same here, getting theis error: Error getting context items from docs: Error: No body returned when downloading from S3 bucket . Even on the continue.dev pre-define url

[marcusnewton]

I am getting this error when using @docs. I assume the LLM is completely hallucinating its response.

[trap20]

Continue: v0.9.214 (pre-release) Version: 1.94.0 (system setup) Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511 Datum: 2024-10-02T13:08:12.626Z Electron: 30.5.1 ElectronBuildId: 10262041 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 Betriebssystem: Windows_NT x64 10.0.22631

Only happens with the "C# Language Reference" for me. Might be related to the # in the title?

[github-actions[bot]]

This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.

[github-actions[bot]]

This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, please reopen + comment and we'll gladly take another look!