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

[browser] Enable GetAsync_ManyDifferentResponseHeaders_ParsedCorrectly #103959

Closed
wants to merge 1 commit into from

Conversation

ilonatommy
Copy link
Member

Fixes #82880. Locally does not fail with the error from the original issue, checking on CI.

@ilonatommy
Copy link
Member Author

/azp run runtime-wasm

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ilonatommy
Copy link
Member Author

My bad: basic CI does not have WasmTestOnNodeJS lib run:
see:

- template: /eng/pipelines/common/templates/wasm-library-tests.yml

it has to wait a bit

@ilonatommy
Copy link
Member Author

The issue is still there, even with a newer NodeJS. No-merge

@ilonatommy ilonatommy closed this Jun 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jul 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript disabled-test The test is disabled in source code against the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[browser] FetchError: request failed, reason: Parse Error: Invalid header value char
1 participant