Skip to content
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

correctly serialize headers and timeout #2071

Merged
merged 4 commits into from
Feb 26, 2025
Merged

Conversation

turbocrime
Copy link
Collaborator

@turbocrime turbocrime commented Feb 21, 2025

Description of Changes

Restrict the use of HeadersInit in a TransportEvent or TransportError to only permit jsonifiable members.

Serialize timeout into the request header as in typical connectrpc.

Technically, an exported type becomes narrower, but the now-omitted member was invalid, and no external API has changed its accepted input/output formats.

Related Issue

Checklist Before Requesting Review

  • I have ensured that any relevant minifront changes do not cause the existing extension to break.

Copy link

changeset-bot bot commented Feb 21, 2025

🦋 Changeset detected

Latest commit: ceca6f0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages
Name Type
@penumbra-zone/transport-dom Patch
minifront Patch
@penumbra-zone/client Patch
@penumbra-zone/services Patch
@penumbra-zone/transport-chrome Patch

Not sure what this means? Click here to learn what changesets are.

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

@turbocrime turbocrime force-pushed the transport-dom-headers branch 2 times, most recently from 5dcd3e5 to 9d32ff2 Compare February 22, 2025 04:28
@turbocrime turbocrime requested a review from TalDerei February 22, 2025 04:31
Copy link
Contributor

@TalDerei TalDerei left a comment

Choose a reason for hiding this comment

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

this looks good, but seems to conflict with #2034 (comment) that was moved to #2058? approving optimistically, and should we narrow the scope of that PR to only disable client streaming?

@turbocrime
Copy link
Collaborator Author

yes, breaking up PR #2058, it was kind of a random collection

@turbocrime turbocrime force-pushed the transport-dom-headers branch 9 times, most recently from 7cba666 to 50e0c6b Compare February 26, 2025 04:18
@turbocrime turbocrime force-pushed the transport-dom-headers branch from 50e0c6b to 38a38ff Compare February 26, 2025 04:43
@turbocrime turbocrime force-pushed the transport-dom-headers branch from 38a38ff to ece8b54 Compare February 26, 2025 04:47
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