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

[wasm] Rework fetch #61639

Merged
merged 8 commits into from
Nov 16, 2021
Merged

[wasm] Rework fetch #61639

merged 8 commits into from
Nov 16, 2021

Conversation

lewing
Copy link
Member

@lewing lewing commented Nov 16, 2021

No description provided.

@lewing lewing requested a review from marek-safar as a code owner November 16, 2021 00:11
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

Copy link
Member

@kg kg left a comment

Choose a reason for hiding this comment

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

Looks fine assuming nothing breaks

return <Response><any> {
ok: true,
ok: false,
Copy link
Member

Choose a reason for hiding this comment

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

Maybe store the error as a property so the caller can find out what the error was without an extra throw+catch

}
else if (ENVIRONMENT_IS_NODE) {
// eslint-disable-next-line @typescript-eslint/no-var-requires
const fs = require("fs");
Copy link
Member

@pavelsavara pavelsavara Nov 16, 2021

Choose a reason for hiding this comment

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

This will do require for each call of the _fetch_asset. I admit the previous implementation had the same issue.

Copy link
Member

@pavelsavara pavelsavara left a comment

Choose a reason for hiding this comment

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

I strongly prefer the async variant for NodeJs. readFileSync is "stop the world and wait for disk" for node engine.

@lewing
Copy link
Member Author

lewing commented Nov 16, 2021

I strongly prefer the async variant for NodeJs. readFileSync is "stop the world and wait for disk" for node engine.

Oddly enough that was entirely accidental, I should be a little more careful about what completions I accept.

@lewing lewing requested a review from pavelsavara November 16, 2021 14:24
@pavelsavara
Copy link
Member

it seems there are lint issue


  D:\a\_work\1\s\src\mono\wasm\runtime\startup.ts
    5:117  warning  'TypedArray' is defined but never used  @typescript-eslint/no-unused-vars
  

@pavelsavara
Copy link
Member

I wonder why only staging pipeline failed, not the runtime pipeline.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants