Handle paid Tempo session SSE fetches#643
Draft
parvahuja wants to merge 1 commit into
Draft
Conversation
commit: |
a523f04 to
c30d9bc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Paid Tempo session SSE streams can request additional vouchers after the initial paid retry has already returned a 200 event stream.
Fetch.frompreviously returned that stream directly, so callers using payment-aware fetch could receive payment control events without the client posting the required voucher credentials.Validation
VITE_TEMPO_NETWORK=none pnpm exec vp test --run src/tempo/session/client/Transports.test.tsVITE_TEMPO_NETWORK=none pnpm exec vp test --run src/client/internal/Fetch.test.ts -t "lets methods wrap post-payment responses"pnpm check:typespnpm checkgit diff --check