Skip to content

test: red check for #3430 params replay e2e (do not merge) - #3447

Closed
james-elicx wants to merge 1 commit into
mainfrom
test/3430-red-check
Closed

james-elicx wants to merge 1 commit into
mainfrom
test/3430-red-check

Conversation

@james-elicx

Copy link
Copy Markdown
Member

Throwaway draft to show the Response Store e2e added in #3430 fails without its runtime fix.

This branch is main plus only the use-cache-params fixture and the regenerates a use-cache value keyed by promise params under its original key e2e from #3430. Expected: @vinext/cloudflare#test fails on assert.notEqual(fresh, first). Will be closed once CI reports.

Adds only the use-cache-params fixture and e2e from #3430 on top of main,
without the runtime fix, to show the test fails.
@pkg-pr-new

pkg-pr-new Bot commented Sep 24, 2026

Copy link
Copy Markdown

Open in StackBlitz

@vinext/cloudflare

npm i https://pkg.pr.new/@vinext/cloudflare@3447

create-vinext-app

npm i https://pkg.pr.new/create-vinext-app@3447

@vinext/types

npm i https://pkg.pr.new/@vinext/types@3447

vinext

npm i https://pkg.pr.new/vinext@3447

@cloudflare/workers-response-store

npm i https://pkg.pr.new/@cloudflare/workers-response-store@3447

commit: 6e4656b

@james-elicx

Copy link
Copy Markdown
Member Author

Red confirmed: regenerates a use-cache value keyed by promise params under its original key fails on main at response-store-adapter.e2e.test.ts:529 (assert.notEqual(fresh, first)); it passes on #3430. Closing.

@james-elicx
james-elicx deleted the test/3430-red-check branch September 24, 2026 17:02
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.

1 participant