Skip to content

Fix incorrect last bytes sent API timing data from nested requests - #65449

Open
Andrew Branch (andrewbranch) wants to merge 1 commit into
microsoft:mainfrom
andrewbranch:sync-ipc-transport-benchmark
Open

Andrew Branch (andrewbranch) wants to merge 1 commit into
microsoft:mainfrom
andrewbranch:sync-ipc-transport-benchmark

Conversation

@andrewbranch

Copy link
Copy Markdown
Member

Noticed while working on something totally unrelated

Copilot AI balanced review requested due to automatic review settings November 12, 2026 00:40
@github-project-automation github-project-automation Bot moved this to Not started in PR Backlog Nov 12, 2026
@typescript-automation typescript-automation Bot added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Nov 12, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified for the nested-request sent-byte timing fix.

No open issues 🎉

What changed in this PR

Fixes sent-byte timing data in the synchronous TypeScript API when a callback issues a nested request.

Changes:

  • Restores the outer request’s sent-byte count when its response arrives.
  • Adds a regression test verifying that a larger nested request does not overwrite the outer request’s recorded size.
File Description
packages/​typescript/​test/​sync/​timing.test.ts Tests sent-byte timing for nested synchronous requests.
packages/​typescript/​src/​api/​syncChannel.ts Recalculates sent bytes from the current request payload before returning its response.

Review effort: Balanced

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

Status: Not started

Development

Successfully merging this pull request may close these issues.

2 participants