microsoft / microsoft/foundry-dev-tools

Extension error when going beyond token limit (o1Preview)

Open
#132 2 comments 0 reactions 1 assignee View on GitHub

@swatDong is already working on this.

Since Dec 17, 2024.

feature request
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
42m
Merged PRs (30d)
29

Description

WRT Version 0.8 of the extension:

  • When using the extension, I was conversing with o1Preview.
  • I then received the 'output_error' (below) in the output panel
  • I understand that I went beyond it's context window, but this should not generate an error. The context window should simply continue rolling and truncate what was sent.

<output_error>
[2024-12-12T23:39:59.505Z] [INFO] Command registration.
Connected to agent:Inference.Service.Agent pipe after retries:1
Finished agent startup...
Agent unlocked
Finished agent startup...
Agent unlocked
Information: Microsoft.Neutron.Rpc.Service.JsonRpcService [2306] 2024-12-13T10:40:01.6479238+11:00 Accepting pipe incoming pipeName:ai.19cd8dc3ab87f0271171b75092552347 numOfSession:2
[2024-12-12T23:40:02.913Z] [INFO] telemetry event:activate_extension sent
[2024-12-12T23:44:07.787Z] [INFO] Loading View: catalogModels
[2024-12-12T23:44:22.259Z] [INFO] Loading View: modelPlayground
[2024-12-13T00:07:12.803Z] [ERROR] Failed to chatStream. provider = "GitHub", model = "o1-preview", errorMessage = "Error: Unable to inference the GitHub model o1-preview due to 413. Request body too large for o1-preview model. Max size: 4000 tokens.", errorType = "c", errorObject = {}
[2024-12-13T00:07:12.804Z] [ERROR] Unable to inference the GitHub model o1-preview due to 413. Request body too large for o1-preview model. Max size: 4000 tokens.
</output_error>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.