Page MenuHomePhabricator
Differential D10047

Use olm WASM with content hash on web in production
ClosedPublic
Actions

Authored by marcin on Nov 27 2023, 2:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 27, 2:05 AM
Unknown Object (File)
Mon, Nov 25, 9:44 AM
Unknown Object (File)
Mon, Nov 25, 7:37 AM
Unknown Object (File)
Tue, Nov 12, 3:43 PM
Unknown Object (File)
Sat, Nov 9, 7:10 PM
Unknown Object (File)
Sat, Nov 9, 2:57 PM
Unknown Object (File)
Wed, Oct 30, 1:21 PM
Unknown Object (File)
Oct 2 2024, 4:38 AM
View All 55 Files
Subscribers
ashoat
tomek

Details

Reviewers
michal
Commits
rCOMM4855a48317c4: Use olm WASM with content hash on web in production
Summary

This differential fixes an urgent Linear issue: https://linear.app/comm/issue/ENG-5895/web-notification-decryption-error. Production web builds will use
olmFilename variable with content hash provided by the keyserver. Development builds will use default olm.wasm filename.

Test Plan
  1. Clear all cache files for localhost:3000/comm. This step is necessary since production builds might have used olm WASM from cache populated by dev builds.
  2. Builds production web app.
  3. Ensure that notifications are encrypted (MariaDB console) and correctly decrypted on the keyserver.

Diff Detail

Repository
rCOMM Comm
Branch
marcin/eng-5895
Lint
No Lint Coverage
Unit
No Test Coverage

Revision Contents
Changeset List

PathSize
web/
push-notif/
4 lines

Diff 33696

View Options

web/push-notif/push-notifs-handler.js

Loading...