Skip to content

Conversation

sjf
Copy link
Contributor

@sjf sjf commented Jul 28, 2025

As described here, int64 cannot be deserialized directly into numbers in Typescript.

Switch these timeout, token budgets and line limit fields to int32 because the range of values should fit in int32.

Replace the Int64Request and response in the RPC updateTerminalConnectionTimeout with request and response messages for this RPC. It is the best practise to have unique request/response messages for each RPC because 1) it means you can update the request or response easily because the message is not shared with other RPCs; and 2) the fields can also have self-documenting names instead of the generic value field name.


Important

Change several ProtoBus fields from int64 to int32 and update updateTerminalConnectionTimeout RPC to use specific request/response messages.

  • Proto Changes:
    • Change shell_integration_timeout, terminal_output_line_limit, fireworks_model_max_completion_tokens, fireworks_model_max_tokens, request_timeout_ms, plan_mode_thinking_budget_tokens, and act_mode_thinking_budget_tokens from int64 to int32 in state.proto.
    • Replace Int64Request and Int64 with UpdateTerminalConnectionTimeoutRequest and UpdateTerminalConnectionTimeoutResponse for updateTerminalConnectionTimeout RPC in state.proto.
  • Controller Changes:
    • Update updateTerminalConnectionTimeout() in updateTerminalConnectionTimeout.ts to use UpdateTerminalConnectionTimeoutRequest and UpdateTerminalConnectionTimeoutResponse.
  • UI Changes:
    • Modify TerminalSettingsSection.tsx to handle UpdateTerminalConnectionTimeoutResponse and update timeout handling logic.

This description was created by Ellipsis for cf61c14. You can customize this summary. It will automatically update as commits are pushed.

Copy link

changeset-bot bot commented Jul 28, 2025

⚠️ No Changeset found

Latest commit: cf61c14

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

…t32.

As described [here](#5174), int64 cannot be deserialized directly into numbers in Typescript.

Switch these timeout and line limit fields to int32 because the range of values should fit in int32.

Replace the Int64Request and response in the RPC `updateTerminalConnectionTimeout` with request and response messages for this RPC. It is the best practise to have unique request/response messages for each RPC because it means you can update the request or response easily because the messages are not shared with other RPCs. The fields can also have self-documenting names instead of the generic `value` field name.
@sjf sjf force-pushed the sjf-jl28-alskdjflskj branch from a3b6153 to 950beab Compare July 28, 2025 20:30
Copy link
Contributor

github-actions bot commented Jul 28, 2025

Coverage Report

Extension Coverage

Base branch: 46%

PR branch: 47%

✅ Coverage increased or remained the same

Webview Coverage

Base branch: 17%

PR branch: 17%

✅ Coverage increased or remained the same

Overall Assessment

Test coverage has been maintained or improved

Last updated: 2025-07-28T21:21:38.685848

@sjf sjf changed the title Change timeout and line limit fields in the ProtoBus from int64 to int32. Change timeout, token budge and line limit fields in the ProtoBus from int64 to int32. Jul 28, 2025
@sjf sjf changed the title Change timeout, token budge and line limit fields in the ProtoBus from int64 to int32. Change timeout, token budget and line limit fields in the ProtoBus from int64 to int32. Jul 28, 2025
@sjf sjf merged commit 6122473 into main Jul 28, 2025
13 checks passed
@sjf sjf deleted the sjf-jl28-alskdjflskj branch July 28, 2025 21:40
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

Successfully merging this pull request may close these issues.

2 participants