-
Notifications
You must be signed in to change notification settings - Fork 57
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
[Error] Please enter your api key, go to https://codegpt.co/ for more information. #142
Comments
Same here :( |
Yeah I don't get it except for it may be an IDE issue. I think updating to the latest VS Code may fix it, but not on Codium ... at least on a Mac it doesn't work. I haven't gotten around to confirming it. |
So I'm on an old 2009 MBP and switched to the latest VS Code ... still doesn't work. I no longer get the error, but now it just returns with an empty reply. Edit: It indeed looks like it accessed the API, looking at the OpenAI dashboard. |
did you updated the extension ? |
@Maol-1997 No, I just installed VS Code from Brew, then installed from the marketplace within the IDE. I think my problem is with my graphics drivers and software. I just glanced at it, but I'm on Monterey 12.5.3 I think it said. Edit: At least for me, I believe if it doesn't show up in the marketplace, then it might not properly work. I didn't notice this plugin in the Codium IDE, so I had to manually install it. I believe that is a clue. |
My understanding is that some 3rd party dependencies cannot be open-sourced with some plugins, and they can only be released for VS Code. Actually I think it's some of the code MS included in it, now that I'm remembering ... probably a little of both. |
Codegpt oficial extension is in vscode only. It uses an vscode encripted storage to store the api keys, maybe in your os you need to send special permissions ? |
Thank you so much, that's just what I needed to hear. The developer should be able to close at least one ticket, and should probably should add the clarification in bold somewhere. |
same issue, and using vs code |
@adepeuf , which version, what platform, and is it the exact issue and error message? |
VS CODE: CODE GPT extension: v2.1.6 Error : althoug I've saved my API key every prompt to code gpt is immediately answered with "Please enter your api key, go to https://codegpt.co/ for more information." and on the bottom right of VS code there is another error message that pops up: "Enter your API KEY to save it securely." |
@adepeuf Your problem is wrong VS Code version, please update to the latest version. 1.78. |
works with 1.78, thank you |
what is my api ?😒 |
Version: 1.79.1 (user setup) I still receiving the following message after entering my api key: I need help please |
I think I got the same problem. I'm using VScodium 1.80 and codeGPT 2.1.9. Whenever I set the API key, it seems it was set correctly. After restart of VScodium, the chat sidebar says I should set my API key (even though I did before). Here's the log, that is thrown by this extension (not sure whether it is related):
|
The problem seems to stem from ChatSidebarProvider, lines 58 onwards. {"_actual":null,"_actualOk":null,"_actualErr":null,"_hasValue":false,"_value":null,"_hasErr":false,"_err":null} which is not an API key. This stems from the fact that |
You're a lifesaver! Created a gist with those changes. Confirmed it's working for OpenAI on an M2 Macbook Pro running VSCodium v1.81.0 https://gist.github.com/silentsilas/c11acff9d65d04f40920ddb782d17195 |
Hello
After the update to 1.81 it works, thanks
Com os melhores cumprimentos | Best regards
[Image]
Tiago Silva Costa | MSc
Chief Executive Officer
Skype: tiagocostanuno
Tlm: +351 917 269 041 , +351 918 069 762
http://virtualcare.pt<https://virtualcare.pt>
UPTEC Asprela I, Rua Alfredo Allen, 461 | 4200-135 Porto
From: Silas ***@***.***>
Date: Friday, 4 August 2023 at 20:36
To: davila7/code-gpt-docs ***@***.***>
Cc: Tiago Silva-Costa ***@***.***>, Comment ***@***.***>
Subject: Re: [davila7/code-gpt-docs] [Error] Please enter your api key, go to https://codegpt.co/ for more information. (Issue #142)
The problem seems to stem from ChatSidebarProvider, lines 58 onwards. The const apiKey is filled with:
{"_actual":null,"_actualOk":null,"_actualErr":null,"_hasValue":false,"_value":null,"_hasErr":false,"_err":null}
which is not an API key. This stems from the fact that context.secrets.get() is an async function, but there is no await. Thus, the constant is filled with a promise... Later the result of the promise is accessed with apiKey.g, which fails. Simple fix: make _update an async function and await for the api key. Use apiKey only, not apiKey.g These changes fixed the plugin for me in VScodium. I'm uncertain whether this change breaks anything else....
You're a lifesaver! Created a gist with those changes. Confirmed it's working for OpenAI on an M2 Macbook Pro running VSCodium v1.81.0
https://gist.github.com/silentsilas/c11acff9d65d04f40920ddb782d17195
—
Reply to this email directly, view it on GitHub<#142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE2F7D4CRINTIHYRRZ2MDTXTVFK5ANCNFSM6AAAAAAXW3TQEY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hi everyone! I hope you're all doing well. Please take a moment to update to the latest version here: Visual Studio Marketplace. Thank you! |
Can you please refactor your code and communicate better errors? I'm getting this even though I've set-up my API key.
The text was updated successfully, but these errors were encountered: