Repository navigation
canSendRequest returns undefined on activation even though constent has been given #213644
Description
Testing #213552
Used Cat sample extension to test this. Please correct me if I misunderstood something
- Added the following code to the end of the
activatemethod (so it runs on activation)
vscode.lm.selectChatModels({ family: 'gpt-3.5-turbo' })!.then(models => {
if (models.length > 0) {
const [first] = models;
const response = context.languageModelAccessInformation.canSendRequest(first)
console.log('Can send request:', response);
} else {
console.log('No chat models available');
}
});
-
Run extension
- Log:
Can send request: undefined=> This is expected, consent has not been given yet
- Log:
-
Send a chat message using the
@catparticipant (@cat Hello World)- Consent is requested => Accept
-
Restart the extension
- 🐍 Log:
Can send request: undefined
- 🐍 Log:
Consent has been given by now, so the expected response would be true?
When sending another @cat Hello World message, consent is not requested again.
Activity
jrieken commentedon May 28, 2024
Nice find!
fixes #213644
fixes #213644 (#213789)
vscodenpa commentedon May 29, 2024
Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting
\closedWith someCommitSha, or directly add theinsiders-releasedlabel if you know this has already been releaased