Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request Failed: Sourcegraph Cody Gateway: unexpected status code 400 #63023

Open
ZebraSu opened this issue Jun 2, 2024 · 2 comments
Open

Request Failed: Sourcegraph Cody Gateway: unexpected status code 400 #63023

ZebraSu opened this issue Jun 2, 2024 · 2 comments

Comments

@ZebraSu
Copy link

ZebraSu commented Jun 2, 2024

  • **Sourcegraph version: 1.20.0
  • **Platform information: vscode 1.89.1 / Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.89.1 Chrome/120.0.6099.291 Electron/28.2.8 Safari/537.36

Steps to reproduce:

  1. Open the cody chat window and enter the text
  2. For the first session, cody returns the content normally, but for the next session cody gets an error

Expected behavior:

Able to converse normally

Actual behavior:

Request Failed: Sourcegraph Cody Gateway: unexpected status code 400: {"error":"request blocked - if you think this is a mistake, please contact [email protected] and reference this ID: 010df187e67388aa2808816e0f334cb1"}

@captainYE1
Copy link

Hello, I encountered the same issue as well. It occurs when using the @ symbol to reference code files, resulting in the same 400 error. Additionally, this problem occasionally arises even when normally initiating a new chat. Apart from Mixtral, which can respond without issues, both Claude and GPT will report errors.

Errors:
Request Failed: Sourcegraph Cody Gateway: unexpected status code 400: {"error":"request blocked - if you think this is a mistake, please contact [email protected] and reference this ID: f686f6a9a149b24e5809dd35a677588b"}

@captainYE1
Copy link

I ran a test and found that if I first use Mixtral and then switch to Claude and GPT, they can generate output normally. I'm not sure what the issue is. I'm using the extension in VSCode, and the version is also 1.20.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants