failed to delete intrinsics

[AidenRourke]

Everything was working fine and then all of a sudden I started to get this message:

Removing intrinsics.Array.@wry/context:Slot

Followed by this error:

failed to delete intrinsics.Array.@wry/context:Slot (TypeError#1)

The messages only appear if I call lockdown()

[erights]

What version of what browser?

[AidenRourke]

Google Chrome, Version 89.0.4389.82 (Official Build) (x86_64)

[erights]

Were you doing anything else in that window or frame before calling lockdown? Can you reproduce it in a fresh window?

[erights]

Could you visit https://ses-demo.netlify.app/demos/console/
Open "More Tools" > "Developer Tools"
select the "Console" tab
refresh the page. What do you see on the console? On my Chrome I see

[AidenRourke]

I don't see it in https://ses-demo.netlify.app/demos/console/

This is what my code looks like

import React from "react";
import ReactDOM from "react-dom";
import "./index.css";
import "ses";

window.lockdown();

ReactDOM.render(
    <div/>,
    document.getElementById("entry")
);

[AidenRourke]

It's weird because it was working fine and then randomly started giving me the error. Like I didn't update my SES version or anything.

[erights]

Curiouser and curiouser. The hits on this web search look suspicious. Many of the hits seem to be about malware. But that doesn't mean much until it is clearer what we're looking at. Nothing is clear yet.

https://www.google.com/search?sxsrf=ALeKk01BHzP4KvzBegjPbcC9-tnMJInx8Q%3A1615854715901&ei=e_xPYNe0Ntj4-gTK1b_YDA&q=Array+%22%40wry%2Fcontext%3ASlot%22&oq=Array+%22%40wry%2Fcontext%3ASlot%22&gs_lcp=Cgdnd3Mtd2l6EANQz64FWM-uBWCYtQVoAXAAeACAAWSIAb0BkgEDMS4xmAEAoAEBqgEHZ3dzLXdpesABAQ&sclient=gws-wiz&ved=0ahUKEwiX3uXyx7PvAhVYvJ4KHcrqD8sQ4dUDCA0&uact=5

[erights]

Attn @warner @kriskowal @dckc @michaelfig

[AidenRourke]

Is there any hack I can use to get rid of this error? I use a locally downloaded version of ses.

[erights]

What happens if you restart your browser?

How are you turning that code into something that runs in your browser? Are you using a bundler or packer or something?

[AidenRourke]

It's basically a stock create-react-app so it uses webpack. I'll try restarting my browser.

[kriskowal]

Looks like https://github.com/benjamn/wryware must be running first. Same author as https://github.com/benjamn/private, which is not SES compatible. They are probably employing similar tricks, which can now all be replaced with a WeakMap or private fields. @AidenRourke Can you trace your app’s dependency graph to see what’s using wryware?

[dckc]

I'm sort of able to reproduce it:

1. npx create-react-app ses612
2. cd ses612; yarn start
3. all is well. React app with spinning log appears
4. yarn add ses
5. add 2 lines to index.js: import 'ses'; and window.lockdown()
6. yarn start

expected behavior: all is well. React app works
actual behavior: blank screen. Error generating stack: Cannot redefine property: info in the console:

[HMR] Waiting for update signal from WDS...
scheduler.development.js:298 [Deprecation] SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021. See https://developer.chrome.com/blog/enabling-shared-array-buffer/ for more details.
(anonymous) @ scheduler.development.js:298
ses.umd.js:4568 Removing intrinsics.Reflect.decorate
ses.umd.js:4568 Removing intrinsics.Reflect.metadata
ses.umd.js:4568 Removing intrinsics.Reflect.defineMetadata
ses.umd.js:4568 Removing intrinsics.Reflect.hasMetadata
ses.umd.js:4568 Removing intrinsics.Reflect.hasOwnMetadata
ses.umd.js:4568 Removing intrinsics.Reflect.getMetadata
ses.umd.js:4568 Removing intrinsics.Reflect.getOwnMetadata
ses.umd.js:4568 Removing intrinsics.Reflect.getMetadataKeys
ses.umd.js:4568 Removing intrinsics.Reflect.getOwnMetadataKeys
ses.umd.js:4568 Removing intrinsics.Reflect.deleteMetadata
react-dom.development.js:789 Uncaught 
index.js:1 The above error occurred in the <App> component:

Error generating stack: Cannot redefine property: info


Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
console.<computed> @ index.js:1
react-dom.development.js:23275 Uncaught 
DevTools failed to load SourceMap: Could not load content for chrome-extension://dmkamcknogkgcdfhhbddcghachkejeap/browser-polyfill.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

[erights]

On the first Removing intrinsics.Array.@wry/context:Slot error, if it reappears:

Is there any hack I can use to get rid of this error? I use a locally downloaded version of ses.

If you don't care if you're still safe after doing that hack, in your download of ses, you can add it to the whitelist. But in order to whitelist it, we need to know what the type of its value is.

In whitelist-intrinsics.js you'll see

      try {
        delete obj[prop];
      } catch (err) {
        if (prop in obj) {
          console.error(`failed to delete ${subPath}`, err);
        } else {
          console.error(`deleting ${subPath} threw`, err);
        }
        throw err;
      }

Change that first call to console.log into

          console.error(`failed to delete ${subPath}: ${typeof obj[prop]}`, err);
          return; // to continue to see all other such errors

and let me know what the new error message says, or messages if these are more than one. Then we should be able to complete the following whitelisting instructions:

In whitelist.js you'll find an entry like

  Array: {
    // Properties of the Array Constructor
    '[[Proto]]': '%FunctionPrototype%',
    from: fn,
    isArray: fn,
    of: fn,
    prototype: '%ArrayPrototype%',
    '@@species': getter,
  },

Add a line at the end, changing it to

  Array: {
    // Properties of the Array Constructor
    '[[Proto]]': '%FunctionPrototype%',
    from: fn,
    isArray: fn,
    of: fn,
    prototype: '%ArrayPrototype%',
    '@@species': getter,
    '@wry/context:Slot': <something depending on what type its value is>
  },