Page MenuHomePhabricator

[web] Deprecate non-worker opaque wasm
ClosedPublic

Authored by michal on Mar 19 2024, 7:34 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 6, 3:10 PM
Unknown Object (File)
Fri, Apr 5, 6:20 PM
Unknown Object (File)
Thu, Apr 4, 7:01 PM
Unknown Object (File)
Wed, Apr 3, 2:32 PM
Unknown Object (File)
Mon, Apr 1, 11:07 PM
Unknown Object (File)
Fri, Mar 29, 8:09 AM
Unknown Object (File)
Mar 28 2024, 1:34 AM
Unknown Object (File)
Mar 27 2024, 6:01 AM
Subscribers

Details

Summary

ENG-7242 : Deprecate opaque WASM for non-worker web context

D11274, as a part of moving the identity client to the shared worker, introduces a new way to host the opaque WASM file for the webworker that is more inline with the rest of the WASM files. This diff removes the previous WASM file hosted for the browser tab JS context.

Depends on D11351

Test Plan

Made sure that in dev and prod there were no errors in the console after loading the webapp.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Mar 19 2024, 7:38 AM
Harbormaster failed remote builds in B27581: Diff 38170!
kamil added inline comments.
web/crypto/opaque-utils.js
20 ↗(On Diff #38170)

I guess you can move this file to /worker directory

This revision is now accepted and ready to land.Mar 19 2024, 8:57 AM
web/app.react.js
89 ↗(On Diff #38189)

Why was this line removed?

web/app.react.js
89 ↗(On Diff #38189)

We no longer use opaque in the browser-tab-JS-context and only in worker (the only places where it is used is web/grpc/identity-service-client-wrapper.js which now is only created on the worker). We longer need to initialize it on the tab context.

web/app.react.js
89 ↗(On Diff #38189)

Thanks for explaining!

I think the reason this line was here in the first place is to try to initialize the module as soon as possible, instead of lazily.

Would it be good to have a similar line in the web worker? Or is it not necessary?

Call opaque as soon as identity client is initialized (this is the first place where we have access to the opaque path on the worker).